Skip to main content
Glama
beiming183-cloud

AutoCAD MCP Server - Codex Edition

entity

Create, query, and modify AutoCAD drawing objects such as lines, circles, polylines, arcs, and more, using operations like list, get, 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?, angle?, scale?, layer?} create_batch — data: {entities: [{type, ...}], continue_on_error?}

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
doc_idNo
pointsNo
strictNo
entity_idNo
operationYes
lease_tokenNo
idempotency_keyNo
expected_revisionNo
worker_generationNo
include_screenshotNo
Behavior2/5

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

The description lists mutating operations (erase, move, scale) and readOnlyHint is false, but it adds no behavioral context beyond operation names. It doesn't disclose that erase is destructive, whether modifications require lease_token or expected_revision, or any side effects. The description adds minimal value beyond the annotations.

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 long but well-structured, organized by operation categories (create, read, modify). It front-loads the summary and each line is informative. While lengthy, it avoids fluff and uses a consistent format, making it reasonably concise for the breadth of functionality.

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 tool is complex with 16 parameters and many operations, but the description leaves gaps: no return value formats, no explanation of generic parameters like lease_token, strict, or expected_revision, and no error semantics. It is sufficient for operation selection but not for full understanding of behavior or outputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by mapping each operation to its relevant parameters (e.g., create_line: x1, y1, x2, y2, layer; create_circle: data with cx, cy, radius). This is essential for the agent to construct valid calls and adds significant meaning beyond the generic schema.

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 'Entity creation, querying, and modification' with a specific resource (entities). It lists concrete operations for create, read, and modify, fully distinguishing it from sibling tools like layer or block. The purpose is immediately evident.

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 implies usage through the enumerated operations but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. For example, it doesn't say 'use layer for layer operations.' It provides context but lacks explicit when-to-use guidance.

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/beiming183-cloud/AutoCAD-MCP'

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