multiCAD-mcp-server

Overview Schema Source Related Servers Discussions Admin

manage_annotations

Create architectural annotations by labeling room centroids with computed areas, generating linear dimension chains, and adding leader callouts in CAD drawings.

Instructions

Create automated architectural annotations, centroid room labels, and linear dimension chains.

Behavior:

Mutation: Mutates drawing by generating and placing new annotation text, dimensions, and leaders.
Persistence: Inserted annotations persist in DWG/DXF database upon save.
Side Effects: Auto-creates destination annotation layers (e.g. A-ANNO-TEXT, A-ANNO-DIMS) if nonexistent.

Usage Guidelines:

When to Use: Call to automatically label room centroids with computed areas (m²), generate overall or wall-by-wall linear dimension chains, or add leader callouts with arrowheads.
Sibling Routing / Alternatives:
- For manually drafting single primitive dimensions or leaders with custom points, use draw_entities(entities="dimension|... / leader|...").
- For modifying, moving, restyling, or deleting existing annotation entities, use manage_entities.
- For room scheduling tables, use manage_entities(operations="area_table|...").

Actions & Parameters:

"label_spaces": Places text label with room name and computed area at centroid of closed room spaces.
"auto_dimension": Generates exterior linear dimension chain along bounding box or wall segments.
"add_leader": Inserts architectural callout leader pointing to specified geometry.

Parameters:

action: Action to perform ("label_spaces", "auto_dimension", "add_leader"). Default: "label_spaces".
handles: Optional entity handle or list of handles to annotate. If None, processes all spaces.
style: Dimensioning style for "auto_dimension" ("overall" for global extents, "segments" for each wall). Default: "overall".
offset: Offset distance in drawing units between geometry and dimension line. Default: 1.0.
text_height: Text height for labels and dimensions in drawing units. Default: 0.35.
prefix: Text prefix added before calculated area value (e.g. "Sup = "). Default: "".
suffix: Text suffix appended after area value. Default: " m²".
layer: Target layer name (default: "A-ANNO-TEXT" for space labels, "A-ANNO-DIMS" for dimensions).
color: Optional color name or ACI number.

Returns: JSON string containing created annotation handles, count, and status.

Input Schema

TableJSON Schema

Name	Required	Default
`color`	No
`layer`	No
`style`	No	overall
`action`	No	label_spaces
`offset`	No
`prefix`	No
`suffix`	No	m²
`handles`	No
`text_height`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that this is a mutation, that results persist to the DWG/DXF on save, and that annotation layers are auto-created as a side effect. It stops short of failure modes, required permissions/active-drawing prerequisites, and undo/rollback semantics, which keeps it from a 5.

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 a one-line purpose, then clearly sectioned Behavior, Usage Guidelines, Actions, Parameters, and Returns. It is long, but the length is justified by 9 parameters; a few lines (e.g. restating defaults already in the schema) are mildly redundant.

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?

Given 9 parameters, no annotations, and an output schema (so return-format detail is optional), the description is nearly complete, covering actions, side effects, and sibling routing. It omits prerequisites like requiring an open/active drawing session and behavior on error, which a mutation tool of this complexity could reasonably state.

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?

Schema description coverage is 0%, so the description must compensate and it does: every parameter is explained with meaning, units, and defaults (offset in drawing units, text_height, prefix/suffix examples, layer defaults per action, style='overall' vs 'segments', handles=None meaning process all spaces). This adds substantial meaning the bare schema lacks.

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?

States a specific verb+resource ('Create automated architectural annotations, centroid room labels, and linear dimension chains') and enumerates the three concrete actions it can perform. It also names the sibling tools it is NOT (draw_entities, manage_entities) so an agent can route correctly without opening schemas.

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?

Explicit 'When to Use' conditions are given (label room centroids with areas, generate dimension chains, add leader callouts) plus a dedicated Sibling Routing section that names draw_entities, manage_entities, and the area_table operation as alternatives with the distinguishing condition for each.

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

Deploy Server