opentakeoff-mcp

Overview Schema Source Related Servers Discussions Admin

find_schedule

Locate schedule tables in a drawing set by kind, returning sheet, title, headers, total-row count, and viewable region so you can view or read the exact table.

Instructions

Locate a schedule table in the set (#87): pass a kind ("room finish", "material"/"finish") and get every matching table's sheet, title, headers, TOTAL row count, and REGION — sized for a view_sheet look or a read_sheet_text pull of exactly the table. A schedule continued across sheets is ONE match whose "parts" list every fragment (base first) with its own viewable region; tables read through rotated headers say so; a table answering for one building carries "building"; a table with delta/REV-marked rows says how many in "revised_rows". Errors with what WAS found when the asked-for kind isn't in the set. Coordinates are image px at render scale 2.0: PDF pt × 2, origin top-left, y down (the browser canvas's native space). Sheet payloads carry dims in both px and pt.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "find_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes	"room finish" (rooms → surface finishes), "finish"/"material" (codes → products), or "equipment" (MEP device schedules — fans, pumps, heaters, AHUs, VAVs, diffusers/grilles/registers — keyed by mark, proven by a powered or air-device column)

Output Schema

Name	Required	Description	Default
`matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.1.31Nov 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / x0 / $ref
```
Removed value: -"#/properties/matches/items/properties/region/properties/x0"
```
- addedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / x0 / type
```
Added value: +"number"
```
- removedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / x1 / $ref
```
Removed value: -"#/properties/matches/items/properties/region/properties/x1"
```
- addedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / x1 / type
```
Added value: +"number"
```
- removedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / y0 / $ref
```
Removed value: -"#/properties/matches/items/properties/region/properties/y0"
```
- addedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / y0 / type
```
Added value: +"number"
```
- removedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / y1 / $ref
```
Removed value: -"#/properties/matches/items/properties/region/properties/y1"
```
- addedOutput schema / properties / matches / items / properties / parts / items / properties / region / properties / y1 / type
```
Added value: +"number"
```
- addedOutput schema / properties / matches / items / properties / parts / items / properties / rows / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / matches / items / properties / parts / items / properties / rows / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / matches / items / properties / revised_rows / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / matches / items / properties / revised_rows / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / matches / items / properties / rows / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / matches / items / properties / rows / minimum
```
Added value: +-9007199254740991
```

Changed1 schema field changedv0.1.21Sep 12, 2026

changedInput schema / properties / kind / description

Previous value: -"\"room finish\" (rooms → surface finishes) or \"finish\"/\"material\" (codes → products)"New value: +"\"room finish\" (rooms → surface finishes), \"finish\"/\"material\" (codes → products), or \"equipment\" (MEP device schedules — fans, pumps, heaters, AHUs, VAVs, diffusers/grilles/registers — keyed by mark, proven by a powered or air-device column)"

Changed1 schema field changedv0.1.18Aug 19, 2026

addedOutput schema / properties / matches / items / properties / revised_rows

Added value: +{
+  "description": "Rows carrying a delta/REV marker — the ink changed there; resolve those tags to see which",
+  "type": "integer"
+}

Changed5 schema fields changedv0.1.12Aug 3, 2026

addedOutput schema / properties / matches / items / properties / building

Added value: +{
+  "description": "The building this table answers for, when its title or sheet names one",
+  "type": "string"
+}

addedOutput schema / properties / matches / items / properties / parts

Added value: +{
+  "description": "Present when the table CONTINUES across sheets ('… SCHEDULE — CONT'D'): every fragment, base first, each with its own viewable region",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "region": {
+        "additionalProperties": false,
+        "properties": {
+          "x0": {
+            "$ref": "#/properties/matches/items/properties/region/properties/x0"
+          },
+          "x1": {
+            "$ref": "#/properties/matches/items/properties/region/properties/x1"
+          },
+          "y0": {
+            "$ref": "#/properties/matches/items/properties/region/properties/y0"
+          },
+          "y1": {
+            "$ref": "#/properties/matches/items/properties/region/properties/y1"
+          }
+        },
+        "required": [
+          "x0",
+          "y0",
+          "x1",
+          "y1"
+        ],
+        "type": "object"
+      },
+      "rows": {
+        "type": "integer"
+      },
+      "sheet": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "sheet",
+      "title",
+      "rows",
+      "region"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / matches / items / properties / region / description

Previous value: -"Pass to view_sheet to look at the table"New value: +"Pass to view_sheet to look at the table (the BASE fragment's region when the table continues)"

addedOutput schema / properties / matches / items / properties / rotated_headers

Added value: +{
+  "description": "true when the column headers were read at a quarter-turn",
+  "type": "boolean"
+}

addedOutput schema / properties / matches / items / properties / rows / description

Added value: +"Total data rows — a continued schedule counts every fragment's rows"

Addedv0.1.9Jul 31, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and discharges it: continued schedules collapse to ONE match with ordered "parts", rotated-header reads are flagged, single-building and revised-row cases surface as fields, and the error path reports what WAS found. It even pins down the coordinate convention (image px at render scale 2.0, PDF pt × 2, top-left origin, y down), which an agent could not infer from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key action and return shape are front-loaded, and the denser clauses (parts ordering, rotated headers, coordinate math) are all load-bearing rather than filler. It is on the long side and the coordinate aside sits mid-sentence, slightly interrupting the scan, but no sentence is expendable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with no annotations, the description covers the match semantics, the multi-fragment case, edge-case fields, the failure mode, and the coordinate space. It restates some return structure that the output schema already carries, but nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents all three kinds in detail, so the baseline applies. The description restates two of the kinds ("room finish", "material"/"finish") but omits "equipment" and adds no matching rules beyond what the schema says, so it neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Locate a schedule table in the set") and enumerates exactly what comes back: sheet, title, headers, TOTAL row count, and REGION. The sibling references to view_sheet and read_sheet_text make the boundary between locating a table and reading it unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "sized for a view_sheet look or a read_sheet_text pull of exactly the table" routes the agent to the right follow-up tools, which is real usage context. It stops short of saying when NOT to use this tool (e.g., when you already know the sheet and just want text), so it is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server