Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

add_dimension

Creates horizontal, vertical, or aligned dimensions between two points, with optional offset and custom text, for labeling distances in AutoCAD drawings.

Instructions

Размер между (x1,y1) и (x2,y2). По умолчанию горизонтальный; vertical=True: вертикальный; aligned=True: параллельный отрезку (наклонный). offset: смещение размерной линии (для aligned: >0 слева от направления 1→2). text: своя подпись, text_height: высота текста (иначе авто). Пересекающиеся подписи разносятся автоматически.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "add_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
textNo
offsetNo
alignedNo
verticalNo
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/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 defaults (horizontal unless overridden, offset default, auto text height) and a non-obvious side effect – overlapping labels are automatically spaced apart. It does not state units, required permissions, or whether it creates a new drawing entity, but the output schema covers the return side.

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?

The description is one dense paragraph that front-loads the core meaning and then walks parameter by parameter with no filler. The telegraphic, semicolon-separated style is efficient, though the abrupt parameter labels reduce readability slightly.

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?

For a 9-parameter mutation tool with no annotations, the description covers all mode flags and the notable auto-spacing behavior, and the output schema handles return values. It stops short of stating units, the default offset value, or prerequisites, which are minor residual gaps.

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 0%, so the description must compensate, and it does: it defines vertical, aligned, offset (including the sign convention for aligned: >0 is left of the 1→2 direction), text, and text_height (auto when null). The four coordinate parameters are only implied as a point pair, and the default offset value is not restated.

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 opening phrase "Размер между (x1,y1) и (x2,y2)" names a specific verb-like action (place a linear dimension) and the resource (two points). It implicitly distinguishes itself from the angular/radial/chain siblings by defining the linear two-point case, but never names those alternatives, so the differentiation stays implicit.

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?

The description explains the three modes (default horizontal, vertical=True, aligned=True) which implies when each applies, but gives no explicit when-to-use vs add_dimension_chain, add_angular_dimension or add_radial_dimension. Guidance is implied rather than stated.

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