Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_ellipse

Creates an elliptical shape in an AutoCAD drawing from center coordinates, X/Y radii, an optional layer, and a rotation angle.

Instructions

Эллипс: центр (cx,cy), полуоси rx (по X) и ry (по Y), rotation: поворот в градусах.

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>",
      "rx": "<rx>",
      "ry": "<ry>"
    },
    "name": "draw_ellipse"
  }
}

Input Schema

NameRequiredDescriptionDefault
cxYes
cyYes
rxYes
ryYes
layerNo0
rotationNo

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?

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about what the call creates, whether it draws into model space or a specified layer, what units cx/cy use, or how it interacts with the current drawing state. Only the rotation unit (degrees) is disclosed, which is a semantic detail rather than a behavioral trait.

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 compact sentence that front-loads the center coordinates and then the radii, with no filler. The dense telegraphic style is appropriate for a low-complexity geometry tool, though it reads as a parameter glossary rather than a description.

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 described, and the geometry semantics are well covered. However, with zero annotation coverage and an undocumented layer parameter, the definition leaves gaps about mutating behavior and layer targeting that matter for correct invocation.

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% and all parameters carry only bare titles, so the description must compensate. It meaningfully explains cx/cy as the center, rx and ry as semi-axes oriented along X and Y respectively, and rotation as degrees — information absent from the schema; only layer is left unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (ellipse) and enumerates its geometric parameters, but never states the action explicitly — the verb comes only from the tool name. It also draws no distinction from closely related siblings such as draw_circle or draw_arc.

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 use an ellipse rather than draw_circle, draw_arc, or draw_polyline, and no prerequisites or context are given. The agent must infer usage entirely from the name.

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