Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_construction

Draws window, door, frame, balcony, loggia, partition, and glazing constructions from measurements in AutoCAD or DXF, using dimensions, layouts, and opening types.

Instructions

Чертёж конструкции по замеру. kind: frame | window | door | vitrazh | balcony | loggia (раздвижное) | partition | generic. frame (любая схема из конструктора): {width,height,outward,view,frame}, frame = {fill:{t,hinge,dir}} или {split:{dir:'v'|'h',sizes:[мм],parts:[...],shtulp?}}; t: glass|panel|turn|tiltturn|tilt|tophung|door|slide, hinge: left|right (петли, вид изнутри), sizes от края рамы до оси импоста. params (мм): window={width,height,profile,outward,sashes:[{width,type,hinge|handle}]} (type: Глухое/Поворотное/Поворотно-откидное/Откидное); door={width,height,side,door_type,outward}; vitrazh={width,height,columns,rows}; balcony={width,height,door_width,door_side}; loggia={width,height,sections}; прочее={width,height,name}. view='outside': вид снаружи.

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": {
      "kind": "<kind>",
      "params": "<params>"
    },
    "name": "draw_construction"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds useful conventions such as millimetre dimensions, hinge direction viewed from inside, and view='outside' meaning seen from outside, but it does not disclose whether entities are created, where they are placed, what layer is used, or other side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, and the content is information-dense with little wasted text. However, the long semicolon-delimited Russian block and compressed notation make it difficult to scan, and a structured list or examples would improve usability.

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?

Given the complex nested params and zero schema description coverage, the description is substantially complete for constructing the parameter object. It still omits important drawing-tool context such as insertion origin, coordinate system, placement relative to existing geometry, and layer or side-effect behavior.

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 so extensively. It defines the kind values and provides detailed nested parameter shapes for frame, window, door, vitrazh, balcony, loggia, and generic constructions, including frame subtree grammar and component enums.

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 clearly states that it draws a construction based on measurements and enumerates the supported kinds (frame, window, door, vitrazh, balcony, loggia, partition, generic). It is distinguishable from generic CAD primitives, though it does not explicitly contrast itself with sibling drawing tools.

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 kind list implies when each construction type should be used, but there is no explicit guidance on when to choose this tool instead of generic primitives such as draw_rectangle or draw_walls. No prerequisites or exclusions are stated.

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