Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_arc

Draws an arc from a center, radius, and start/end angles, or from three points defining its start, middle, and end.

Instructions

Дуга. Либо центр (cx,cy), радиус r и углы start_angle..end_angle в градусах против часовой, либо points: три точки [[x,y] начало, [x,y] на дуге, [x,y] конец].

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

Input Schema

NameRequiredDescriptionDefault
rNo
cxNo
cyNo
layerNo0
pointsNo
end_angleNo
start_angleNo

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?

With no annotations, the description carries the full burden, and it does disclose two important behavioral facts: angles are in degrees and measured counterclockwise. It omits whether the arc is added to the active drawing, what layer it lands on, and the failure mode for conflicting inputs, so a mutation tool remains partially opaque.

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?

Two dense sentences with the primary geometric definition front-loaded and the alternative mode second; nothing is redundant. The 'either/or' framing is efficient, though the run-on structure makes it slightly harder to scan than a bulleted split would be.

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, and the geometry inputs are well covered. Gaps remain for a 7-parameter drawing tool: the layer parameter, coordinate units, and the precedence rule when both center and points are provided.

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 r, cx, cy, start_angle, end_angle, and the exact nested structure of points ([[x,y] start, [x,y] on arc, [x,y] end]). Only the layer parameter is left unexplained, and coordinate units are unstated.

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 gives a specific verb+resource (draw an arc) and immediately distinguishes its two construction modes, so an agent knows exactly what geometry results. It does not explicitly differentiate itself from near-siblings like draw_circle or draw_spline, which keeps it from a 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?

The two mutually exclusive input strategies (center+radius+angles vs. three points) are stated clearly, which is real usage guidance at the parameter level. However, there is no statement of when to prefer this tool over draw_polyline/draw_spline for curved geometry, and no note about what happens if both modes are supplied.

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