Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_polygon

Draws a regular polygon in AutoCAD by specifying center, radius, and sides, with options for inscribed radius and rotation angle for precise placement.

Instructions

Правильный многоугольник: центр, радиус r, число сторон sides. inscribed=True: r до вершин, False: r до середины сторон. rotation: угол первой вершины (90 = вершина вверху).

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": {
      "cx": "<cx>",
      "cy": "<cy>",
      "r": "<r>",
      "sides": "<sides>"
    },
    "name": "draw_polygon"
  }
}

Input Schema

NameRequiredDescriptionDefault
rYes
cxYes
cyYes
layerNo0
sidesYes
rotationNo
inscribedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/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 real geometric behavior: the two inscribed modes (radius to vertices vs. midpoints of edges) and the rotation convention with the 90 = vertex-up default. However, it says nothing about write-side behavior — that entities are added to the active drawing, how layer '0' default behaves, or error conditions — and an output schema exists so return values need not be covered.

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 compact clauses front-loaded with the shape identity, then the two non-obvious parameter semantics; no filler or repetition. The telegraphic style is efficient, though the colon-heavy phrasing makes it slightly harder to parse than plain sentences.

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 7-parameter geometry tool with 0% schema coverage and no annotations, the description is nearly sufficient: it explains the geometry-defining parameters and defaults that an agent would otherwise guess wrong. The remaining gap is 'layer' and any statement of where the polygon is drawn.

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 coverage is 0%, so the description must supply meaning, and it does for six of seven parameters: it names the center (cx/cy), r, sides, and — most valuably — defines inscribed and rotation semantics that the schema titles alone would not convey. Only 'layer' (default '0') is left completely 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?

The description states a concrete verb+resource: a regular polygon defined by center, radius r, and a side count. That immediately separates it from draw_circle (no sides) and draw_rectangle (no side count), though it never names a sibling explicitly or covers draw_polyline, which is the nearest overlapping concept.

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 when-to-use or when-not-to-use guidance at all — nothing tells the agent to prefer this over draw_polyline with closed points, or over draw_rectangle/draw_circle for 4-sided or circular shapes. Usage is only implied by the shape description.

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