opentakeoff-mcp

Overview Schema Source Related Servers Discussions Admin

annotate

Place notes, revision clouds, highlights, callouts, arrows, bubbles, and dimensions on construction sheets to mark up work. Attach to finish tags to include in scope.

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 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

Name	Required	Description
`r`	No	Bubble radius (image px); omitted → the canvas default (2% of sheet width)
`at`	No	Anchor point (image px) — text, callout, and bubble (the circle's center)
`to`	No	Arrow head / dimension end (image px)
`from`	No	Arrow tail / dimension start (image px)
`rect`	No	Corners (image px) — cloud and highlight
`text`	No	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
`type`	Yes	cloud/highlight need rect; text/callout/bubble need at; callout also needs target; arrow and dimension need from + to
`sheet`	Yes	Sheet name or number, as sheet_info reports it
`target`	No	What a callout's leader line points at (image px)
`condition`	No	Finish tag to attach this note to, e.g. 'CPT-1' (minted on first use). Omit for an unattached sheet note

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`note`	Yes
`text`	Yes
`type`	Yes
`sheet`	Yes
`condition`	Yes
`length_lf`	No	Dimension only: the measured length (real feet) the annotation will label itself with
`condition_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.1.11Aug 2, 2026

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"
+}

Changed7 schema fields changedv0.1.9Jul 31, 2026

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"
+]

Addedv0.1.6Jul 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses the dimension scale gate and its refusal behavior, the tag-minting-on-first-touch behavior, the no-review-gate rule, coordinate space (image px at 2.0 scale, PDF pt x2, origin top-left), and colour/PDF/report propagation. The main omission is any statement about what happens on failure for non-dimension types or whether annotations can be re-edited, so it is not quite exhaustive.

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

Conciseness3/5

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

It is front-loaded with the core purpose, but the paragraph is dense, parenthesis-heavy and carries a reference marker (#150) plus redundant restatement ('it touches no quantity' appears twice in different words). For a 10-parameter, 7-type tool some length is warranted, but several clauses do not earn their place.

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?

An output schema exists, so return values need not be documented, and the description covers everything else an agent needs: type-to-parameter requirements, coordinate conventions, gate behavior, and condition/scope semantics. Nothing material to calling this correctly is missing.

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 already 100%, so the baseline would be 3; however the description adds genuine meaning beyond the schema by explaining the dimension's measured-endpoint semantics and the scale gate, the bubble radius default, and the condition tag's scope consequences. The per-type parameter mapping largely restates what the enum description already says, keeping this short of a 5.

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 first sentence states a specific verb and resource ('Place an annotation on a sheet') and immediately differentiates it from the measurement tools ('a note ABOUT the work, never a measurement of it'). It then enumerates all seven annotation types and their geometry, so an agent can tell exactly what this does versus nearby siblings like measure_polygon or edit_annotation.

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?

It states explicitly when to attach a note to a condition tag ('what makes it part of that SCOPE rather than a floating remark') and when to omit it ('for a note about the sheet itself'). It also names the alternative route for dimensions ('set_scale first') and clarifies there is no review gate, covering when-not as well as when.

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