Skip to content

compose_request_details

Request additional detail in the next view hierarchy snapshot. Call this when you need more information than the default compact element list provides. The next turn’s view hierarchy will include the requested details for ALL elements, then automatically revert to the compact format on subsequent turns.

Available detail types: - BOUNDS: Include bounding box coordinates {x,y,w,h} for each element. Useful for spatial reasoning, determining element positions, checking viewport visibility, or disambiguating visually similar elements by location.

Source

  • Kind: class-backed
  • Class: xyz.block.trailblaze.compose.driver.tools.ComposeRequestDetailsTool

Contract

  • Visible to LLM: yes (surface_to_llm: true)
  • Recordable: no (is_recordable: false)
  • Host-only: no (requires_host: false)

Input schema

Required parameters

  • include — ToolParameterType.List( itemsType = ToolParameterType.Enum( entries = [BOUNDS] ) ) List of detail types to include in the next view hierarchy. Supported: [“BOUNDS”]. Example: [“BOUNDS”] to see element positions.

Output

Returns: string (opaque text content)

Typed result schemas (kind: query | action, MCP structuredContent) are not yet carried by the resolved manifest — this section will gain detail when that lands.