Skip to main content
Glama
haianhdskt-boop

autocad-ai-mcp

Add Entities

add_entities

Batch add geometric entities like lines, circles, arcs, polylines, text, and dimensions to a DXF modelspace. Specify file path and entity list to populate drawings efficiently.

Instructions

Batch add geometric entities to a DXF drawing's modelspace.
Supported entity types:
- line: {"type": "line", "start": [x1, y1], "end": [x2, y2], "layer": "WALL", "color": 1}
- circle: {"type": "circle", "center": [x, y], "radius": r, "layer": "HOLES"}
- arc: {"type": "arc", "center": [x, y], "radius": r, "start_angle": a1, "end_angle": a2}
- lwpolyline: {"type": "lwpolyline", "points": [[x1, y1], [x2, y2], ...], "is_closed": true}
- rectangle: {"type": "rectangle", "corner1": [x1, y1], "corner2": [x2, y2], "layer": "FRAME"}
- text: {"type": "text", "text": "Label", "insert": [x, y], "height": 3.5}
- mtext: {"type": "mtext", "text": "Multi

Line", "insert": [x, y], "height": 3.5} - point: {"type": "point", "location": [x, y]} - ellipse: {"type": "ellipse", "center": [x, y], "major_axis": [dx, dy, 0], "ratio": 0.5} - dimension_linear: {"type": "dimension_linear", "base": [x, y], "p1": [x1, y1], "p2": [x2, y2], "text": "100mm"} - block_reference: {"type": "block_reference", "block_name": "DOOR", "insert": [x, y], "scale": 1.0, "rotation": 0.0}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entitiesYes
file_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose the batch-add behavior, the modelspace target, and a rich catalog of supported entity shapes. However, it does not mention side effects like whether entities are appended versus replacing existing content, whether the file must already exist, or how invalid entities are handled.

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 highly information-dense: every entity type line adds necessary formatting detail that the schema lacks. The content is front-loaded with the core action and modelspace target before the examples. A more compact representation would risk losing critical type-specific parameter information.

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?

Given the high complexity of the entities parameter and the complete absence of schema detail, the description does enough for an agent to invoke the tool with correct entity payloads. It stops short of explaining file-path prerequisites, behavior with existing drawings, and response/error semantics, but the provided examples cover the primary invoke-correctly needs.

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?

Schema coverage is 0%, and the schema itself only defines an opaque array of objects. The description compensates fully by providing detailed JSON examples for every supported entity type, including required fields like start/end, center/radius, and insert points. This is essential for constructing valid calls.

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 states a specific action ('Batch add geometric entities') and a precise resource ('a DXF drawing's modelspace'). It also enumerates the supported entity types, which clearly separates this tool from siblings like add_layer, delete_entities, and query_drawing_entities.

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 clearly implies when to use the tool: whenever geometric entities need to be added to a drawing. However, it does not explicitly state when not to use it or mention alternatives like execute_ezdxf_script for more custom entity creation.

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

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/haianhdskt-boop/autocad-ai-mcp'

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