Skip to main content
Glama
CaeliaEve

AutoCAD MCP Ultra

by CaeliaEve

Measure Entity

analysis_measure_entity
Read-onlyIdempotent

Measure any measurable drawing entity by handle, returning exact area and geometry. Uses real geometry to include arc bulges, and flags flattened or self-intersecting results for accuracy.

Instructions

Measure something already in the drawing, by handle.

Reads the real geometry, so polyline bulges (arc edges) are included — reading vertices back and shoelacing them yourself loses 28% of the area on a semicircular edge, silently.

Measurable: LWPOLYLINE, 2D POLYLINE, CIRCLE, ELLIPSE, SPLINE, HATCH, SOLID, TRACE, 3DFACE. REGION and 3DSOLID need the live COM backend (their area is in ACIS data ezdxf cannot evaluate) and refuse with capability: "measure_area_acis". LINE/TEXT/INSERT bound no area on any engine and are a plain error, not a capability gap.

The payload states its own accuracy: exact is false when the shape had to be flattened (then flatten_tolerance says how finely), assumed_closed is true when an open boundary was closed the way AutoCAD's AREA does, and self_intersecting warns when the shoelace cancelled crossed lobes — a bowtie measures 0.0 and that number is worse than useless unflagged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesEntity handle (hex string) from create/list/select
flatten_toleranceNoMax chord deviation when geometry has no closed form (splines, partial ellipses)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations declare readOnlyHint and idempotentHint, and the description adds substantial behavioral context beyond that: it reads real geometry including polyline bulges, exposes accuracy flags (exact, assumed_closed, self_intersecting), and documents distinct error modes for unsupported entities. This is exactly the kind of disclosure that helps an agent predict side effects and failure behavior.

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?

Every sentence earns its place: the purpose is front-loaded, the geometry-fidelity caveat is meaningful, the supported/unsupported type lists are compact, and the accuracy-flag explanation is essential. The description is longer than average but not wasteful — its length is justified by the tool's complexity.

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 an output schema and clear annotations, the description covers supported input types, capability-gated failures, plain errors, accuracy semantics, and the source of the handle parameter. Nothing an agent needs to call this tool correctly or interpret its results is left unexplained.

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 description coverage is 100%, so the schema already documents both parameters. The description adds useful context by explaining how flatten_tolerance relates to the reported accuracy flag and why bulge-aware measurement matters, reinforcing the parameter's purpose beyond the raw schema text.

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 and resource — measure an entity by handle — and enumerates the exact geometry types it supports. The description clearly centers on area measurement while distinguishing it from generic listing/stat tools by its geometry-fidelity guarantees. An agent can tell what this tool does without ambiguity.

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

Usage Guidelines4/5

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

Provides strong applicability context: lists measurable entity types, explicitly calls out LINE/TEXT/INSERT as errors, and explains that REGION/3DSOLID require a COM capability. It stops short of naming sibling tools like analysis_measure_area or analysis_measure_distance and saying when to prefer them, but the when-to-use and when-not-to-use guidance is otherwise explicit.

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/CaeliaEve/autocad-mcp-ultra'

If you have feedback or need assistance with the MCP directory API, please join our Discord server