multiCAD-mcp-server

Overview Schema Source Related Servers Discussions Admin

draw_entities

Create 2D/3D CAD geometry, text, dimensions, leaders, and tables from shorthand or JSON, with automatic layer creation and centroid/extents calculation.

Instructions

Create new 2D/3D geometric primitives, text, dimensions, leaders, and native tables.

Behavior:

Mutation: Mutates the drawing database by creating and appending new entities.
Persistence: Changes persist in the active drawing database and are written to DWG/DXF file upon save.
Side Effects: Auto-creates destination layers if they do not exist. Automatically computes centroid and extents.

Usage Guidelines:

When to Use: Call whenever creating new geometry from scratch (lines, walls, circles, rectangles, polylines, text labels, architectural dimensions, multi-arrow leaders, or schedule tables).
Sibling Routing / Alternatives:
- For modifying, transforming (move, rotate, scale), restyling, or deleting existing entities, use manage_entities.
- For inserting reusable component blocks (doors, windows, symbols) or creating block definitions, use manage_blocks.
- For creating paperspace presentation sheets, title blocks, and viewports, use manage_layouts.
- For attaching external DWG references or raster underlays, use manage_xrefs.

Shorthand Grammar (one entity specification per line):

line|start|end|color|layer → line|0,0|10,10|red|walls
circle|center|radius|color → circle|5,5|3|blue
rect|corner1|corner2|color → rect|0,0|20,15
text|pos|text|height|color → text|5,5|Hello|2.5
arc|center|radius|start|end → arc|0,0|5|0|90
polyline|points(;)|closed|color → polyline|0,0;10,10;20,0|closed
spline|points(;)|closed|color → spline|0,0;5,10;10,0
dimension|start|end|color → dimension|0,0|10,0
leader|points|text|height|color|layer → leader|0,0;10,10|Note|2.5|red
leader|group1~~group2~~...|text|height|color → leader|0,0;10,10~~0,0;-10,10|Note
table|ins|rows|cols|row_h|col_w|title|headers|data → table|0,0|4|3|3|15|Precios|Item;Cant;Val|Acero;10;150~~Mano;5;120

Defaults: color=white, layer=0. Coordinates: "x,y" or "x,y,z". Points in a polyline/leader: semicolon-separated "0,0;10,10".

Parameters:

entities: Shorthand string (one command per line) or JSON array of entity specification objects.

Returns: JSON string with created entity handles, status, and summary count.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entities`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that the drawing database is mutated, that changes persist to DWG/DXF on save, and that destination layers are auto-created and centroid/extents auto-computed. It stops short of stating what happens on malformed input (atomic vs. partial creation), whether the operation is undoable, or any permission requirements.

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?

Long but front-loaded and fully sectioned: purpose, behavior, usage, grammar, parameters, returns. Every line of the shorthand grammar table earns its place by specifying a distinct callable entity form, and no sentence is redundant with another.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 explained, yet the description still summarizes them. For a one-parameter, annotation-free tool with a free-form string DSL, the mutation semantics, side effects, routing, and input grammar are all covered — nothing needed to invoke it correctly is missing.

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% (the single 'entities' parameter is typed only as string), so the description must compensate and does: it defines the per-line shorthand grammar with ten concrete examples, coordinate formats ('x,y' / 'x,y,z', semicolon-separated point lists), and defaults (color=white, layer=0). This is far beyond what the schema conveys.

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 first sentence states a specific verb (Create) and enumerates the concrete resource set (2D/3D primitives, text, dimensions, leaders, native tables). Combined with the explicit sibling routing section, an agent can distinguish this from manage_entities, manage_blocks, and manage_layouts without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'When to Use' clause plus four named alternatives (manage_entities, manage_blocks, manage_layouts, manage_xrefs) each with the condition that selects it. Nothing about tool selection is left to inference.

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

Deploy Server