Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

measure

Calculates object length, area, or perimeter from a CAD handle, or distance between two points, so you can retrieve dimensions directly from AutoCAD geometry.

Instructions

Измерить: длина/площадь/периметр объекта по handle, или расстояние между точками (x1,y1)-(x2,y2).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "measure"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1No
x2No
y1No
y2No
handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing about units, coordinate system, error behavior, or whether it only reads geometry. Only the bare measurement intent is conveyed; the read-only nature must be inferred from the word 'measure'.

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?

A single front-loaded sentence covering both modes with no filler. It is terse to the point of omitting mode-selection rules, but nothing written is wasted.

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?

An output schema exists so return values need not be described, and the two modes are named. Still, for a five-parameter tool with zero schema description coverage and no annotations, the definition leaves the agent guessing about valid parameter combinations and preconditions such as whether the handle must exist.

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 description coverage is 0%, and the description is the only place that gives meaning to handle, x1/y1, x2/y2 by grouping them into two measurement modes. It still fails to state that the parameters are mutually exclusive mode selectors, that all are optional/nullable in the schema, or which combination is required.

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?

The description names a specific verb ('Измерить') and two concrete resources/modes: length/area/perimeter of an object by handle, and distance between two points. It is clearly distinguishable from the many draw_* and add_dimension siblings, though it does not explicitly contrast itself with them.

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?

Two usage modes are implied by the description (handle-based object measurement vs. point-to-point distance), which gives an agent enough to pick inputs. However, there is no statement of when to prefer this over dimension-adding siblings, and no guidance on invalid combinations or preconditions.

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