Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_mtext

Draw multi-line MTEXT in AutoCAD at a given point, with paragraph width wrapping, optional height, alignment, and layer control.

Instructions

Многострочный текст (MTEXT) от точки (x,y) (левый верх; align='center': центр). Строки через \n, width: ширина абзаца (0 = без переноса), height: авто, если не указана.

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": {
      "x": "<x>",
      "y": "<y>",
      "text": "<text>"
    },
    "name": "draw_mtext"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
textYes
alignNoleft
layerNoTEXT
widthNo
heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/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 it does disclose real geometry behavior: the anchor point semantics, \n line splitting, paragraph wrapping driven by width, and height being auto-computed when omitted. It omits anything about layer defaults, coordinate space, whether existing entities can be affected, and that this is a drawing mutation on the current document.

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 sentence plus parentheticals, front-loaded with the resource and coordinates and then the wrapping rules. Nearly every clause earns its place; the telegraphic style is efficient, though the nesting of three parenthetical explanations makes it slightly harder to scan.

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?

For a 7-parameter drawing mutation with zero schema coverage and no annotations, the description covers the geometric essentials and needs no return-value detail because an output schema exists. It still leaves the layer parameter and the full align value set unexplained, which an agent needs to call it correctly.

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, and it does for x/y anchor meaning, text newline handling, width (0 = no wrap) and height (auto). However 'align' is only partially explained (center case, no mention of left/right variants) and 'layer' is entirely undocumented in both schema and description.

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 verb+resource: draws multiline MTEXT at point (x,y), with explicit note about the insertion anchor being top-left and center when align='center'. An agent immediately knows this creates multi-line text, unlike draw_text (single-line), though the description never explicitly names or contrasts that sibling.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no named alternative (e.g. draw_text for single-line labels). The word 'Многострочный' hints that this is the choice for wrapped/multi-paragraph text, but that routing must be inferred rather than read.

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