Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

add_radial_dimension

Adds radius or diameter dimensions to circles and arcs using center/radius or a handle, with a selectable leader angle and optional custom text.

Instructions

Радиус или диаметр (diameter=True) окружности/дуги: центр (cx,cy) и r, либо handle окружности/дуги. angle: направление выноски в градусах.

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": "add_radial_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
rNo
cxNo
cyNo
textNo
angleNo
handleNo
diameterNo
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden and it only partially does so. It describes the geometric content of the dimension and the two ways to identify the source entity, which is useful, but never states that this creates/mutates a drawing entity, what happens with an invalid handle, or whether the circle must already exist.

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 dense sentence that leads with what is drawn and then gives the input alternatives; nothing is wasted. It is a sentence fragment without an explicit verb, which slightly reduces readability.

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?

Output schema exists, so return values need not be explained, and the geometry inputs are adequately covered. Still missing for a drawing-mutating CAD tool: that it creates an entity, error behavior for unresolved handles, and the meaning of text/text_height overrides.

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% across 8 parameters, so the description is the only source of meaning, and it explains six of them: diameter, cx, cy, r, handle, and angle (with units in degrees). Critically it conveys the alternative relationship between handle mode and center+radius mode, which the schema cannot express. Only text and text_height are left undefined.

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 the concrete resource (radius/diameter dimension of a circle or arc) and its two input modes (center cx,cy with r, or a handle). Together with the tool name an agent can tell what is produced. It does not explicitly contrast with siblings such as add_angular_dimension or add_dimension, so it stops short of 5.

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?

Usage is implied rather than stated: the description makes clear the tool applies to circles and arcs and offers the diameter=True switch plus the handle-vs-coordinates choice. There is no explicit guidance on when to pick this over add_dimension, add_angular_dimension, or add_dimension_chain, and no prerequisites are mentioned.

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