opentakeoff-mcp

Overview Schema Source Related Servers Discussions Admin

find_schedule

Find schedule tables in a plan set by kind (room finish, finish/material, equipment). Returns each match's sheet, title, headers, total row count, and region to view or read.

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.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.2/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers rich behavioral detail: continued schedules are one match with a parts list, rotated headers are flagged, building-specific tables carry a 'building' attribute, delta/REV-marked tables report revised_rows, errors include what was found, and the coordinate system is fully specified (image px at scale 2.0, origin top-left, y down). This gives the agent a clear mental model of edge cases and output structure.

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 description is a single, dense paragraph that front-loads the tool's purpose and then layers on critical edge-case behavior and coordinate conventions. Every sentence contributes useful information, though the length and lack of structural breaks (e.g., bullets) slightly reduce readability.

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?

Given the complexity of schedule finding and the absence of annotations, the description covers purpose, return shape, edge cases (continuations, rotations, building, revised rows), error behavior, and coordinate system. An output schema exists, so return values need not be fully spelled out, but the description still provides sufficient context for correct invocation.

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 description coverage is 100%, so the schema already defines the 'kind' parameter and its allowed values. The description repeats some of these values but omits 'equipment' (which is detailed in the schema), adding no meaningful semantics beyond what the schema provides. Baseline 3 is appropriate.

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?

The description states a specific verb (Locate) and resource (schedule table), and details exactly what is returned (sheet, title, headers, TOTAL row count, REGION). It distinguishes from siblings by positioning the output for subsequent view_sheet or read_sheet_text calls.

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

Usage Guidelines3/5

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

It implies usage by saying results are 'sized for a view_sheet look or a read_sheet_text pull of exactly the table,' which suggests it's a preparatory step. However, it does not explicitly state when to use this tool versus alternatives like find_text or sweep_schedule_row, leaving the agent to infer the context.

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