Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_order

Creates a multi-item construction order in AutoCAD, laying out items in a row from an origin with position labels, a specification table, and an optional customer header.

Instructions

Заказ из нескольких конструкций одной командой: items [{kind, params, name?, qty?}] (kind/params как в draw_construction), раскладка в ряд от (x,y), подписи «Поз. N» и таблица-спецификация (поз., изделие, Ш×В, площадь м², створки/открывание, кол-во). customer {client,address}: в заголовок.

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": {
      "items": "<items>"
    },
    "name": "draw_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
specNo
itemsYes
customerNo
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/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 it does disclose the generated artifacts in detail: row layout anchored at (x,y), 'Поз. N' labels, and a specification table whose exact columns (pos., product, W×H, area m², sashes/opening, qty) are enumerated, plus the customer block going into the header. It stops short of stating that this is a mutating drawing operation, its failure behavior, or how items map to row spacing.

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?

A single dense paragraph with the core action first, then layout, then generated artifacts, then the customer header — no filler. The compact brace notation for items and customer is efficient, though it makes the text terse enough that a reader must parse two payload shapes inline.

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?

An output schema exists, so return values need no explanation, and the description adequately covers what is drawn and labeled. It is thin for a 6-parameter composite tool with a free-form items array: the meaning of 'spec' and 'text_height', the units/spacing of the row layout, and the behavior of the open-ended item objects are all left unaddressed.

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

Parameters3/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; it does well for the required 'items' by giving the shape {kind, params, name?, qty?} and ties 'customer' {client,address} to the header, while x/y are only implicitly the layout origin. Two parameters remain unexplained: 'spec' (a boolean that plainly toggles the specification table but is never named) and 'text_height', and the item sub-fields are deferred entirely to draw_construction.

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?

States a specific action on a specific resource: builds an order of several constructions in a single command, laid out in a row with position labels and a specification table. The phrase 'из нескольких конструкций одной командой' implicitly distinguishes it from draw_construction for a single item, though the contrast is never made explicit.

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 'multiple constructions at once' framing and the cross-reference '(kind/params как в draw_construction)' point an agent toward the right sibling and show the item vocabulary is shared. It never states when not to use it (e.g., a single construction should go to draw_construction) or any prerequisite such as an open drawing.

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