Skip to main content
Glama
gpt2nndk

AutoCAD MCP Server

by gpt2nndk

entity

Create, query, and modify AutoCAD drawing objects like lines, circles, and polylines. Supports operations to add, list, count, and edit with layer and coordinate attributes.

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 enumerates read and modify operations, and the annotations already signal readOnlyHint=false. It does not disclose side effects such as whether modifications are permanent, destructive actions like erase are irreversible, or how screenshot capture works. It adds the operation list but not deeper behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured into Create, Read, and Modify sections with each operation on a single line. It is front-loaded with a summary line and contains no filler. Every sentence earns its place in conveying the operation set and parameter usage.

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?

The description covers all operations and their parameters, which is comprehensive for a multi-operation tool. It omits the include_screenshot parameter and some operation-specific nuances (e.g., what fillet radius means), but given the output schema exists and annotations are present, it is sufficiently complete. The missing screenshot behavior is a minor gap.

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?

The schema provides zero descriptions for its 10 parameters, but the description maps each operation to its relevant parameters (e.g., create_line — x1, y1, x2, y2, layer?). This is valuable beyond the schema. However, it does not fully explain nested data objects (e.g., for create_hatch, data: {pattern?} is cryptic), so it earns a 4 rather than a 5.

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 opens with 'Entity creation, querying, and modification,' clearly stating the tool's purpose and scope. It then enumerates specific operations (create_line, list, erase, etc.), which distinguishes it from sibling tools like layer or drawing. This is a specific verb+resource statement with clear scope.

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 lists all sub-operations, implying when to use the tool for entity tasks. However, it does not explicitly state when to prefer this tool over siblings or provide exclusions (e.g., 'for layer management, use the layer tool'). The context is clear but lacks explicit guidance on alternatives.

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/gpt2nndk/autocad-mcp-nndk'

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