Skip to main content
Glama
Kentucky-ai

opentakeoff-mcp

by Kentucky-ai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

find_schedule

Find schedule tables in a plan set by type: pass 'room finish' or 'material' to get sheet, title, headers, TOTAL row count, and image region for each match.

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
NameRequiredDescriptionDefault
kindYes"room finish" (rooms → surface finishes) or "finish"/"material" (codes → products)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchesYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.1.18
    • 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"
+}
  2. Changed5 schema fields changedv0.1.12
    • 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"
  3. Addedv0.1.9

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries full burden and excels. It discloses how schedules are matched (including continued schedules as one match with parts), handling of rotated headers, building-specific tables, revised rows, and coordinate system details (px at render scale 2.0, origin top-left, y down). Error messages are explained, and sheet payload dimensions are mentioned. This is highly transparent.

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

Conciseness5/5

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

The description is long but densely packed with essential information. It front-loads the main purpose and then systematically covers edge cases and technical details. Every sentence adds value—no filler or repetition. The structure is logical and efficient.

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 tool's complexity and the presence of an output schema, the description is complete. It explains the result structure (parts, building, revised_rows), error handling, coordinate system, and sheet payload dimensions. No critical aspect is missing; users know exactly what to expect and how to use the tool.

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

Parameters4/5

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

Schema coverage is 100% for the single 'kind' parameter, so baseline is 3. The description adds contextual meaning: it explains that 'room finish' corresponds to rooms→surface finishes and 'finish'/'material' to codes→products, and connects the parameter to the tool's overall purpose. This extra explanation justifies a 4, though the schema already covers the literal values.

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 clearly states the tool's purpose: to locate schedule tables in a set by passing a kind, and it lists exactly what information is returned (sheet, title, headers, TOTAL row count, REGION). It distinguishes from siblings by referencing view_sheet and read_sheet_text usage and detailing edge cases (multi-sheet schedules, rotated headers, building-specific tables). This is specific and unambiguous.

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

Usage Guidelines5/5

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

The description explicitly explains when to use the tool: to find schedules for viewing or reading. It explains the 'kind' parameter choices and their meanings ('room finish' vs 'finish'/'material'), and describes the output structure that guides downstream actions. It also covers error behavior when the kind isn't found, giving clear expectations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kentucky-ai/opentakeoff'

If you have feedback or need assistance with the MCP directory API, please join our Discord server