opentakeoff-mcp

Overview Schema Source Related Servers Discussions Admin

sheet_info

Retrieve sheet dimensions, vector segment count, scale status, and shape count to verify plan readiness for takeoff.

Instructions

Sheet detail: dims (px and pt), vector segment count, whether the sheet has vector linework (measure_polygon runs on it; get_sheet_vectors returns the strokes), scale status, the detected scale suggestion, and this sheet's committed shape count. 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
`sheet`	Yes	Sheet key ("plan.pdf", "plan.pdf#2") or title-block number ("A-101")

Output Schema

TableJSON Schema

Name	Required	Description
`upp`	No	Real feet per image px at render scale 2.0 — present once the scale is set
`page`	Yes	1-based page number
`sheet`	Yes	Sheet key: page 1 is the bare file name ("plan.pdf"), pages 2+ are "plan.pdf#2"
`layers`	Yes	The sheet's PDF layer table (#85) — [] when no Optional Content survived export (every engine path then runs the heuristics unchanged)
`width_pt`	Yes
`width_px`	Yes	Image px at render scale 2.0 — the coordinate space every tool speaks
`height_pt`	Yes
`height_px`	Yes
`scale_set`	Yes
`seg_count`	Yes	Vector segment count
`shape_count`	Yes	Committed shapes on this sheet
`sheet_number`	No	Title-block sheet number ("A-101") where detected
`detected_scale`	No	Drawn scale note read off the sheet — a suggestion, never auto-applied
`multiple_scales`	No	Several DISTINCT scale notes on this sheet (#153) — enlarged plans/details likely
`has_vector_linework`	Yes	one_click needs vector linework

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.9Jul 31, 2026

addedOutput schema / properties / layers

Added value: +{
+  "description": "The sheet's PDF layer table (#85) — [] when no Optional Content survived export (every engine path then runs the heuristics unchanged)",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "confidence": {
+        "description": "0..1 — how sure the name classifier is",
+        "type": "number"
+      },
+      "id": {
+        "description": "Optional Content Group id — pass to one_click/detect_rooms layers.include/exclude",
+        "type": "string"
+      },
+      "name": {
+        "description": "The CAD layer name as exported (e.g. A-WALL-FULL)",
+        "type": "string"
+      },
+      "role": {
+        "description": "What this layer's linework IS to a takeoff (lib/layers.ts) — boundary/structure plot hard, pattern/annotation/demolition are excluded, unknown falls back to the hatch heuristics",
+        "enum": [
+          "boundary",
+          "finish-pattern",
+          "annotation",
+          "structure",
+          "demolition",
+          "unknown"
+        ],
+        "type": "string"
+      },
+      "seg_count": {
+        "description": "Segments this layer owns on this sheet",
+        "type": "integer"
+      },
+      "visible": {
+        "description": "Default-config visibility — a hidden layer's ink is excluded outright (or you trace demolition)",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "role",
+      "confidence",
+      "visible",
+      "seg_count"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / multiple_scales

Added value: +{
+  "const": true,
+  "description": "Several DISTINCT scale notes on this sheet (#153) — enlarged plans/details likely",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "sheet",
-  "page",
-  "width_pt",
-  "height_pt",
-  "width_px",
-  "height_px",
-  "seg_count",
-  "has_vector_linework",
-  "scale_set",
-  "shape_count"
-]New value: +[
+  "sheet",
+  "page",
+  "width_pt",
+  "height_pt",
+  "width_px",
+  "height_px",
+  "seg_count",
+  "has_vector_linework",
+  "scale_set",
+  "shape_count",
+  "layers"
+]

Addedv0.1.5Jul 23, 2026
Removedv0.1.4Jul 21, 2026

Changed1 schema field changedv0.1.2Jul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "detected_scale": {
+      "description": "Drawn scale note read off the sheet — a suggestion, never auto-applied",
+      "type": "string"
+    },
+    "has_vector_linework": {
+      "description": "one_click needs vector linework",
+      "type": "boolean"
+    },
+    "height_pt": {
+      "type": "number"
+    },
+    "height_px": {
+      "type": "number"
+    },
+    "page": {
+      "description": "1-based page number",
+      "type": "integer"
+    },
+    "scale_set": {
+      "type": "boolean"
+    },
+    "seg_count": {
+      "description": "Vector segment count",
+      "type": "integer"
+    },
+    "shape_count": {
+      "description": "Committed shapes on this sheet",
+      "type": "integer"
+    },
+    "sheet": {
+      "description": "Sheet key: page 1 is the bare file name (\"plan.pdf\"), pages 2+ are \"plan.pdf#2\"",
+      "type": "string"
+    },
+    "sheet_number": {
+      "description": "Title-block sheet number (\"A-101\") where detected",
+      "type": "string"
+    },
+    "upp": {
+      "description": "Real feet per image px at render scale 2.0 — present once the scale is set",
+      "type": "number"
+    },
+    "width_pt": {
+      "type": "number"
+    },
+    "width_px": {
+      "description": "Image px at render scale 2.0 — the coordinate space every tool speaks",
+      "type": "number"
+    }
+  },
+  "required": [
+    "sheet",
+    "page",
+    "width_pt",
+    "height_pt",
+    "width_px",
+    "height_px",
+    "seg_count",
+    "has_vector_linework",
+    "scale_set",
+    "shape_count"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden, but 'Sheet detail' implies a pure read and it discloses genuinely useful behavioral context: the pixel coordinate space, render scale 2.0, PDF pt × 2, top-left origin, y-down. It stops short of stating side-effect freedom, auth needs, or caching/perf traits.

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?

Front-loaded with the return inventory, then the coordinate-space note. It is dense and largely earns its sentences, though the nested parentheticals (

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

Completeness4/5

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

An output schema exists, so the description does not strictly need to enumerate return fields, yet doing so helps an agent decide whether to call it. Combined with the coordinate-space note, it is complete enough for a single-parameter reader, with only the sibling-routing gap lingering.

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 'sheet' parameter is fully documented in the schema with accepted key formats. The description adds nothing about the parameter, so the schema does all the work and the baseline 3 applies.

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

Purpose4/5

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

The description enumerates exactly what this tool returns (dims in px/pt, vector segment count, vector-linework flag, scale status, scale suggestion, committed shape count), so an agent knows it is a per-sheet metadata reader. It is scoped to a single sheet, though it never names the sibling it is not (sheet_context, view_sheet, get_sheet_vectors) to sharpen the boundary.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description merely notes that measure_polygon runs on sheets with vector linework and get_sheet_vectors returns strokes, which is incidental context rather than a routing rule between these closely-related siblings.

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