Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_walls

Creates wall plans from centerline points with thickness and door/window openings, supporting closed contours and separate WALLS, DOORS, and WINDOWS layers.

Instructions

СТЕНЫ ПЛАНА по осевой линии points [[x,y],...] толщиной thickness (мм), closed: замкнутый контур. openings: проёмы [{segment: № участка с 0, offset: от начала участка до края проёма, width, type: door|window|opening, swing: left|right (сторона открывания двери относительно направления участка), hinge: start|end}]. Двери с дугой открывания, окна тремя линиями. Слои WALLS, DOORS, WINDOWS.

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": {
      "points": "<points>"
    },
    "name": "draw_walls"
  }
}

Input Schema

NameRequiredDescriptionDefault
closedNo
pointsYes
openingsNo
thicknessNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that geometry is placed on specific layers (WALLS, DOORS, WINDOWS), that doors get a swing arc and windows are drawn with three lines, and that thickness is in millimeters. What it does not say is whether existing geometry is affected, whether the operation is additive or destructive, or what units the points themselves use.

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?

Everything is packed into a few dense clauses with no filler, and the core purpose is front-loaded. The telegraphic, abbreviation-heavy style (№ участка, мм) is efficient but slightly slows parsing for an agent reading it cold.

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 4-parameter geometry tool with an output schema (so return values need not be described), the definition covers every parameter including the nested openings object, and states the resulting layers. The main residual gap is the coordinate unit for points and whether the call alters or overwrites existing entities.

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 description coverage is 0%, so the description must compensate and it does: points are the centerline coordinates, thickness is in mm, closed makes a closed contour, and openings are fully specified with segment index (0-based), offset from segment start to opening edge, width, a type enum of door|window|opening, swing of left|right relative to segment direction, and hinge of start|end. That is enum-level detail the bare schema does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource: it draws plan walls along a centerline polyline, with thickness, optional closure, and openings rendered as doors (with swing arcs) or windows (three lines). This is far more specific than a generic draw_line/draw_polyline sibling. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4 rather than 5.

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 rather than stated: the wall/opening vocabulary signals architectural plan drafting, and the WALLS/DOORS/WINDOWS layer output hints at that workflow. There is no explicit when-to-use vs when-not-to-use guidance, and no mention of alternatives such as draw_polyline for plain linework or prerequisites like an active layer.

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