Skip to main content
Glama
Sign In
opentakeoff-mcp

opentakeoff-mcp

by Kentucky-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sheet_info

Retrieve a plan sheet's dimensions, vector linework, scale status, and committed shape count to verify scale and measurement readiness.

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.

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": {
      "sheet": "<sheet>"
    },
    "name": "sheet_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetYesSheet key ("plan.pdf", "plan.pdf#2") or title-block number ("A-101")

Output Schema

NameRequiredDescriptionDefault
uppNoReal feet per image px at render scale 2.0 — present once the scale is set
pageYes1-based page number
sheetYesSheet key: page 1 is the bare file name ("plan.pdf"), pages 2+ are "plan.pdf#2"
layersYesThe sheet's PDF layer table (#85) — [] when no Optional Content survived export (every engine path then runs the heuristics unchanged)
width_ptYes
width_pxYesImage px at render scale 2.0 — the coordinate space every tool speaks
height_ptYes
height_pxYes
scale_setYes
seg_countYesVector segment count
shape_countYesCommitted shapes on this sheet
sheet_numberNoTitle-block sheet number ("A-101") where detected
detected_scaleNoDrawn scale note read off the sheet — a suggestion, never auto-applied
multiple_scalesNoSeveral DISTINCT scale notes on this sheet (#153) — enlarged plans/details likely
has_vector_lineworkYesone_click needs vector linework

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.31
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / layers / items / properties / seg_count / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / layers / items / properties / seg_count / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / page / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / seg_count / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / seg_count / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / shape_count / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / shape_count / minimum
      Added value: +-9007199254740991
  2. Changed3 schema fields changedv0.1.9
    • 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"
+]
  3. Addedv0.1.5
  4. Removedv0.1.4
  5. Changed1 schema field changedv0.1.2
    • 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"
+}
  6. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implicitly signals a read-only metadata lookup through the returned-field list and adds genuine behavioral context (scale status, detected scale suggestion, committed shape count), but never states read-only/exact-safety, permissions, or cost, and a 'committed shape count' could imply write proximity that is left unexplained.

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 resource label and a dense field list, then a compact coordinate-convention note. The parenthetical cross-references and the closing sentence about carrying dims in px and pt are somewhat redundant, but nothing is padded or vague.

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

Completeness3/5

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

With an output schema present, most of the text re-explains return values rather than filling gaps. What it does uniquely add — the render-scale 2.0 coordinate mapping and top-left/y-down convention — is valuable, but the missing piece is guidance on when this beats sheet_context or view_sheet for sheet orientation.

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% for the single required 'sheet' parameter, and the schema itself documents the accepted key forms ("plan.pdf", "plan.pdf#2", "A-101"). The description adds no further meaning about acceptable sheet identifiers, so 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?

Opening phrase "Sheet detail:" plus an enumerated field list makes clear this returns per-sheet metadata (dims, vector counts, scale status, shape count). It distinguishes itself from get_sheet_vectors ("returns the strokes") and measure_polygon ("runs on it"), though it never contrasts with sheet_context, which sounds closely related.

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?

Usage is only implied: an agent infers it should call this to learn a sheet's dimensions, vector-linework status, and scale state before measuring. There is no explicit "use this when..." and no exclusion naming sheet_context or view_sheet as alternatives, leaving the sibling choice to inference.

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

Deploy Server

Other Tools