Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_axes

Draws coordination axes for building plans using specified x/y spacings, custom labels, and dimension lines per GOST 21.101.

Instructions

КООРДИНАЦИОННЫЕ ОСИ (ГОСТ 21.101): x_spacings: шаги вертикальных осей слева направо (марки 1, 2, 3...), y_spacings: шаги горизонтальных осей снизу вверх (марки А, Б, В... без Ё, З, Й, О, Х, Ц, Ч, Щ, Ъ, Ы, Ь). x/y: положение первой оси. Штрихпунктир, марки в кружках, размеры между осями и общий. both_sides: марки с двух сторон. x_labels/y_labels: свои марки.

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": {
      "x_spacings": "<x_spacings>",
      "y_spacings": "<y_spacings>"
    },
    "name": "draw_axes"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
x_labelsNo
y_labelsNo
both_sidesNo
dimensionsNo
x_spacingsYes
y_spacingsYes
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/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 the dash-dot line style, marks in circles, per-axis and overall dimension lines, and the labeling alphabet rule (excluding Ё, З, Й, О, Х, Ц, Ч, Щ, Ъ, Ы, Ь). It omits what happens when the `dimensions` flag is false and how `text_height` affects output, but the visual/behavioral profile is largely covered, and the output schema covers return values.

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 tool identity and organized parameter-by-parameter with colons; nearly every clause carries information. It is a dense run-on sentence rather than structured prose, but little 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?

For a 9-parameter tool with an output schema, most needed semantics are present, but `dimensions` (which defaults to true and controls the dimension lines the description advertises) and `text_height` are never addressed, and no defaults are mentioned. Also, the description is in Russian while the tool and schema are English, adding an extra interpretation step for some agents.

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 explains 7 of 9 parameters with meaning beyond the titles: direction and numbering of x_spacings (left to right, 1,2,3...) and y_spacings (bottom to top, А,Б,В...), x/y as the first axis position, label overrides, and both_sides. The `dimensions` and `text_height` parameters are left unexplained.

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?

Opens with a specific resource and scope ("КООРДИНАЦИОННЫЕ ОСИ (ГОСТ 21.101)") and then explains the axis-spacing model, so an agent can tell this draws a grid of coordination axes rather than a generic line or polyline. It does not name any sibling drawing tool for contrast, so differentiation comes only from the domain description.

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

Usage Guidelines2/5

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

The GOST reference hints that this is for construction drawings, but there is no explicit when-to-use, when-not-to-use, or alternative (e.g., plain draw_line for non-standard axes). The agent must infer usage entirely from the standard cited.

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