Skip to main content
Glama
ks40-academy

autocad-mcp

by ks40-academy

entity

Create, query, and modify geometric shapes in AutoCAD drawings, including lines, circles, arcs, polylines, and operations like move, rotate, scale, and erase.

Instructions

Entity creation, querying, and modification.

Create operations: create_line — x1, y1, x2, y2, layer? create_circle — data: {cx, cy, radius}, layer? create_polyline — points: [[x,y],...], data: {closed?}, layer? create_rectangle — x1, y1, x2, y2, layer? create_arc — data: {cx, cy, radius, start_angle, end_angle}, layer? create_ellipse — data: {cx, cy, major_x, major_y, ratio}, layer? create_mtext — data: {x, y, width, text, height?}, layer? create_hatch — entity_id, data: {pattern?}

Read operations: list — layer? → list entities count — layer? → count entities get — entity_id → entity details

Modify operations: copy — entity_id, data: {dx, dy} move — entity_id, data: {dx, dy} rotate — entity_id, data: {cx, cy, angle} scale — entity_id, data: {cx, cy, factor} mirror — entity_id, x1, y1, x2, y2 offset — entity_id, data: {distance} array — entity_id, data: {rows, cols, row_dist, col_dist} fillet — data: {id1, id2, radius} chamfer — data: {id1, id2, dist1, dist2} erase — entity_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1No
x2No
y1No
y2No
dataNo
layerNo
pointsNo
entity_idNo
operationYes
include_screenshotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description lists mutating operations (move, erase, copy) and details their parameters, which goes beyond the simple readOnlyHint=false annotation. However, it does not disclose side effects (e.g., erase is destructive), error conditions, or any required permissions, leaving behavioral gaps.

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 description is well-structured with clear section headers and compact per-operation signatures. It is front-loaded with a summary line and avoids redundant prose. It is long, but each line is necessary to cover the many operations.

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?

The description covers all operation signatures, but for a tool with 10 parameters and many distinct operations, it lacks higher-level context such as prerequisite conditions (e.g., an open drawing), return value behavior, and any caveats about destructive operations. The presence of an output schema mitigates the return value gap, but other contextual details remain missing.

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?

With 0% schema coverage, the description carries the full burden of explaining parameters. It does this well by mapping each operation to its specific parameters, including nested data fields like fillet's {id1, id2, radius}. However, it omits the include_screenshot parameter and doesn't explain the meaning of '?' in the signatures.

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

Purpose5/5

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

The description clearly states the tool's function as 'Entity creation, querying, and modification' and lists all supported operations (create_line, list, move, erase, etc.), making its scope unambiguous and distinguishing it from sibling tools like layer, block, or drawing.

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 description groups operations into Create, Read, and Modify, implying when each operation should be used. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusionary guidance or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ks40-academy/autocad-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server