Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

add_angular_dimension

Adds an angular dimension to an AutoCAD drawing using a vertex and two side points, with optional text, text height, and arc radius.

Instructions

Угловой размер: вершина (vx,vy) и точки на сторонах угла (x1,y1), (x2,y2); угол меряется от первой стороны ко второй против часовой. radius: радиус дуги размера (по умолчанию 0.6 от короткой стороны).

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": {
      "vx": "<vx>",
      "vy": "<vy>",
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "add_angular_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
vxYes
vyYes
x1Yes
x2Yes
y1Yes
y2Yes
textNo
radiusNo
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, but it never states that invoking this tool adds an angular dimension entity to the drawing or what side effects, persistence, or permissions are involved. It does disclose two useful behavioral details: the counterclockwise measurement convention and the default radius of 0.6 times the short 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 definition is a compact, front-loaded sentence with semicolon-separated clauses that each add relevant geometry information. It is dense but efficient, with no obvious filler.

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 explained. However, for a 9-parameter, no-annotation drawing mutation, the description omits what the tool actually does to the drawing and leaves text/text_height undefined, making it only partially complete.

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%, so the description must compensate. It explains the six required geometry parameters well and clarifies the radius default, but it says nothing about text or text_height, leaving two optional parameters undocumented.

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 defines the exact geometric resource: an angular dimension with a vertex and two side points. It distinguishes the tool from linear and radial dimension siblings by specifying angle measurement from the first side to the second counterclockwise. The only weakness is that it never explicitly says 'adds' or 'creates' the dimension, leaving the action implied by the tool name.

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?

There is no guidance on when to choose this tool over add_dimension, add_dimension_chain, or add_radial_dimension. The description supplies geometry semantics but no usage context, prerequisites, or exclusions.

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