> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bedrock.cv/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule Lookup

> Cross-reference features with schedules.

## User Prompt

> "What are the specs for door 104?"

## Tool Call Sequence

<Steps>
  <Step title="Find the door feature">
    **Call:** `Query`

    ```json theme={null}
    {
      "entity": "feature",
      "project_id": "proj_oak",
      "type": "door",
      "label": "104"
    }
    ```

    **Response:**

    ```json theme={null}
    {
      "count": 1,
      "items": [
        {
          "id": "ftr_d104",
          "type": "door",
          "label": "104",
          "bounds": { "type": "bbox", "xmin": 310, "ymin": 550, "xmax": 330, "ymax": 580 },
          "confidence": 0.96,
          "uri": "storage://features/ftr_d104/crop.png",
          "metadata": { "swing": "left", "width": "3'-0\"" },
          "block": { "id": "blk_a101_plan", "type": "Plan", "identifier": "1", "sheet_number": "A-101" },
          "parent": { "id": "ftr_rm102", "type": "room", "label": "102" },
          "relations": [
            {
              "relation_type": "scheduled_in",
              "target": {
                "entity_type": "block",
                "id": "blk_door_sched",
                "type": "Schedule",
                "label": "DOOR SCHEDULE",
                "sheet_number": "A-501"
              },
              "metadata": { "row_key": "104" }
            },
            {
              "relation_type": "defined_by",
              "target": {
                "entity_type": "feature",
                "id": "ftr_leg_d1",
                "type": "legend_entry",
                "label": "Single Door",
                "sheet_number": "A-101"
              },
              "metadata": null
            }
          ]
        }
      ]
    }
    ```

    **What the agent learns:** Door 104 is in Room 102 on sheet A-101. It has a `scheduled_in` relation pointing to the door schedule block (`blk_door_sched`) with `row_key: "104"`. The agent knows exactly which block to query and which row to extract.
  </Step>

  <Step title="Fetch the schedule metadata">
    **Call:** `Query`

    ```json theme={null}
    {
      "entity": "block",
      "project_id": "proj_oak",
      "id": "blk_door_sched",
      "include": ["metadata"]
    }
    ```

    **Response:**

    ```json theme={null}
    {
      "count": 1,
      "items": [
        {
          "id": "blk_door_sched",
          "type": "Schedule",
          "identifier": null,
          "name": "DOOR SCHEDULE",
          "uri": "storage://blocks/blk_door_sched/image.png",
          "confidence": 0.97,
          "sheet": { "id": "sh_a501", "sheet_number": "A-501", "discipline": "A" },
          "drawing": { "id": "dr_arch_b", "name": "Arch Set Rev B" },
          "relations": [],
          "metadata": {
            "rows": {
              "104": {
                "size": "3070",
                "material": "HM",
                "fire_rating": "45-min",
                "hardware_set": "HW-3"
              }
            }
          }
        }
      ]
    }
    ```

    **What the agent learns:** Row 104 in the door schedule contains the full specs: size 3070, hollow metal, 45-minute fire rating, hardware set HW-3.
  </Step>
</Steps>

## Agent Response

> **Door 104** is located in Room 102 on sheet A-101. Here are the specs from the Door Schedule on A-501:
>
> | Property     | Value                |
> | ------------ | -------------------- |
> | Size         | 3'-0" x 7'-0" (3070) |
> | Material     | Hollow Metal (HM)    |
> | Fire Rating  | 45 minutes           |
> | Hardware Set | HW-3                 |
> | Swing        | Left                 |
> | Symbol       | Single Door          |

## Summary

| Metric        | Value                                                                                                                                                    |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tool calls    | **2**                                                                                                                                                    |
| Tools used    | `Query` (feature) then `Query` (block)                                                                                                                   |
| Key technique | The `scheduled_in` relation on the feature includes `row_key`, so the agent knows exactly which schedule row to read. No searching or guessing required. |