Skip to main content
Glama
Kentucky-ai

opentakeoff-mcp

by Kentucky-ai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

annotate

Add revision clouds, callouts, arrows, bubbles, and dimensions to plan sheets. Attach notes to finish tags so they become part of the scope and appear in the report.

Instructions

Place an annotation on a sheet — a note ABOUT the work, never a measurement of it. Types: cloud and highlight take rect:[[x0,y0],[x1,y1]] (a revision cloud around an area, a highlight box over it), text takes at:[x,y], callout takes at:[x,y] plus target:[x,y] (the point its leader aims at), arrow takes from:[x,y] and to:[x,y] (tail and head — plank/seam direction, the markup flooring drawings use most; #150), bubble takes at:[x,y] plus optional r (a keynote/detail circle carrying centered text), dimension takes from:[x,y] and to:[x,y] (its two measured endpoints) and labels itself with the length between them at the sheet's scale — drawn as a dimension line with end ticks and the measurement centered. A dimension states a REAL length, so it is the one annotation the scale gate applies to: on an unscaled sheet it refuses exactly like the measure tools (set_scale first) rather than dressing a px figure up as feet. It still touches no quantity — a dimension is a note about a distance, not a takeoff line item.

Pass condition to attach the note to a finish tag, which is what makes it part of that SCOPE rather than a floating remark: it then wears the condition's colour on the canvas and in the marked-set PDF, and travels with it into the report. The tag is minted on first touch like one_click/measure_polygon, so you can annotate CPT-1 before anything is traced for it. Omit condition for a note about the sheet itself.

No review gate: the pencil-not-ink rule exists to stop an agent inventing geometry, and a cloud reading "verify substrate" is not geometry. It touches no quantity. 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
rNoBubble radius (image px); omitted → the canvas default (2% of sheet width)
atNoAnchor point (image px) — text, callout, and bubble (the circle's center)
toNoArrow head / dimension end (image px)
fromNoArrow tail / dimension start (image px)
rectNoCorners (image px) — cloud and highlight
textNoThe note. A cloud with no text still reads as 'look here'; a bubble's text draws centered in the circle; a dimension appends it after the measured length
typeYescloud/highlight need rect; text/callout/bubble need at; callout also needs target; arrow and dimension need from + to
sheetYesSheet name or number, as sheet_info reports it
targetNoWhat a callout's leader line points at (image px)
conditionNoFinish tag to attach this note to, e.g. 'CPT-1' (minted on first use). Omit for an unattached sheet note

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
noteYes
textYes
typeYes
sheetYes
conditionYes
length_lfNoDimension only: the measured length (real feet) the annotation will label itself with
condition_idYes

Schema Changelog

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

  1. Changed6 schema fields changedv0.1.11
    • changedInput schema / properties / from / description
      Previous value: -"Arrow tail (image px)"New value: +"Arrow tail / dimension start (image px)"
    • changedInput schema / properties / text / description
      Previous value: -"The note. A cloud with no text still reads as 'look here'; a bubble's text draws centered in the circle"New value: +"The note. A cloud with no text still reads as 'look here'; a bubble's text draws centered in the circle; a dimension appends it after the measured length"
    • changedInput schema / properties / to / description
      Previous value: -"Arrow head — what it points at (image px)"New value: +"Arrow head / dimension end (image px)"
    • changedInput schema / properties / type / description
      Previous value: -"cloud/highlight need rect; text/callout/bubble need at; callout also needs target; arrow needs from + to"New value: +"cloud/highlight need rect; text/callout/bubble need at; callout also needs target; arrow and dimension need from + to"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "cloud",
-  "text",
-  "callout",
-  "highlight",
-  "arrow",
-  "bubble"
-]New value: +[
+  "cloud",
+  "text",
+  "callout",
+  "highlight",
+  "arrow",
+  "bubble",
+  "dimension"
+]
    • addedOutput schema / properties / length_lf
      Added value: +{
+  "description": "Dimension only: the measured length (real feet) the annotation will label itself with",
+  "type": "number"
+}
  2. Changed7 schema fields changedv0.1.9
    • changedInput schema / properties / at / description
      Previous value: -"Anchor point (image px) — text and callout"New value: +"Anchor point (image px) — text, callout, and bubble (the circle's center)"
    • addedInput schema / properties / from
      Added value: +{
+  "$ref": "#/properties/at",
+  "description": "Arrow tail (image px)"
+}
    • addedInput schema / properties / r
      Added value: +{
+  "description": "Bubble radius (image px); omitted → the canvas default (2% of sheet width)",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / text / description
      Previous value: -"The note. A cloud with no text still reads as 'look here'"New value: +"The note. A cloud with no text still reads as 'look here'; a bubble's text draws centered in the circle"
    • addedInput schema / properties / to
      Added value: +{
+  "$ref": "#/properties/at",
+  "description": "Arrow head — what it points at (image px)"
+}
    • changedInput schema / properties / type / description
      Previous value: -"cloud/highlight need rect; text/callout need at; callout also needs target"New value: +"cloud/highlight need rect; text/callout/bubble need at; callout also needs target; arrow needs from + to"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "cloud",
-  "text",
-  "callout",
-  "highlight"
-]New value: +[
+  "cloud",
+  "text",
+  "callout",
+  "highlight",
+  "arrow",
+  "bubble"
+]
  3. Addedv0.1.6

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility for disclosing behavior, and it does so richly. It reveals the no-review-gate policy and the pencil-not-ink rationale, the coordinate system ('image px at render scale 2.0: PDF pt × 2, origin top-left, y down'), the scale-gate refusal for dimensions on unscaled sheets, and tag minting on first touch. This goes far beyond typical descriptions.

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 every sentence is purposeful: it covers the core purpose, each annotation type's specific parameters, behavior under scale gate, condition attachment semantics, and coordinate conventions. It is front-loaded with the main purpose and progressively adds detail in a logical flow. No redundancy or filler.

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 7 annotation types, 10 parameters, and interaction with scale/condition/review gates, this description is remarkably complete. It addresses all parameter roles, edge cases (unscaled dimension refusal, tag minting, condition color), coordinate system, and the tool's relationship to quantity takeoff. An output schema exists, so return values need not be spelled out, and the description is sufficient for correct invocation.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds substantial meaning beyond the raw schema. It explains the geometric roles of rect for cloud/highlight, target for callout, from/to for arrow and dimension, and at for text/callout/bubble. It also clarifies that dimension labels itself with the measured length and appends text after it, which is not evident from the schema alone. This elevates the semantics significantly.

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 opens with a clear verb and resource: 'Place an annotation on a sheet' and immediately distinguishes its purpose: 'a note ABOUT the work, never a measurement of it.' This contrasts with sibling measurement tools like measure_line and measure_surface. It also enumerates the specific annotation types, leaving no ambiguity about what the tool produces.

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 provides explicit when-to-use guidance: annotations are for notes, not measurements, and the dimension type is singled out as the one annotation subject to the scale gate, with instructions to set_scale first. It also explains when to omit condition ('for a note about the sheet itself') and how condition attachment ties to a finish tag, referencing sibling tools like one_click/measure_polygon for tag minting. This gives clear decision support.

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