AutoCAD MCP

autocad_draw_wall

Draw walls along centerline paths as parallel faces with thickness, end caps, and closed-loop support, converting vertices into CAD wall geometry.

Instructions

Draw a wall along a centerline path as two parallel faces (+ end caps).

Args: params (DrawWallInput): - points (list[Point]): centerline vertices (2-200). - thickness (float): wall thickness (default 100 drawing units). - closed (bool): closed loop, no end caps (default false). - layer (str): wall layer (default 'WALLS').

Returns: str: JSON {"status", "type": "WALL", "length", "thickness", "faces": {"left", "right"}, "end_caps": [...]}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "autocad_draw_wall"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description is free to add geometry-level behavior, which it does: end caps are suppressed for closed loops and the target layer is auto-created. It does not restate mutation/idempotency semantics, which is acceptable given 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?

Front-loaded one-line summary, then Args/Returns sections that are scannable and free of filler. The Args block is partially redundant with the schema but not wasteful enough to hurt.

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?

For a single-composite-argument drawing operation with an output schema, safety annotations, and a fully documented nested schema, the description covers purpose, inputs, and result shape. The only real gap is comparative guidance against its sibling drawing primitives.

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 prose docstring enumerates every nested field of the single `params` object with types and defaults (points 2-200, thickness default 100, closed default false, layer default 'WALLS'), compensating for the top-level `params` property having no description of its own. Most of this duplicates the nested schema, but it makes the composite argument legible at a glance.

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?

Names a specific verb and resource ("Draw a wall along a centerline path") and describes the resulting geometry (two parallel faces plus end caps). This distinguishes it from the generic autocad_create_polyline / autocad_create_line siblings without needing to open a schema.

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?

Usage is implied by the geometry description (a centerline-based wall), but there is no explicit when-to-use or when-not-to-use guidance relative to the many nearby siblings (autocad_create_polyline, autocad_draw_room, autocad_add_door). No prerequisites or ordering constraints are stated.

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

Deploy Server