Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_text

Draws text at specified X/Y coordinates in AutoCAD drawings using Arial Cyrillic, with optional height, alignment, and layer settings.

Instructions

Текст в точке (x,y), шрифт Arial (кириллица). height: высота в мм; если не указана, авто по масштабу (см. set_annotation_scale). align: 'center' или 'left'.

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_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
textYes
alignNoleft
layerNoTEXT
heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/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 real behavior: the fixed Arial/Cyrillic font, the fact that height is optional and auto-derived from the annotation scale, and the accepted align values. However, it says nothing about the default TEXT layer, the effect of drawing on existing entities, or required drawing context, which matters for a mutation tool with zero annotation coverage.

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?

Very compact and front-loaded: position, then font, then the two optional parameters that need interpretation. Every phrase carries information, with only minor terseness in the clipped 'height:' / 'align:' fragments.

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?

Because an output schema exists, return values need not be described. Still, for a six-parameter mutation tool with no annotations, the description omits the layer parameter and offers no sibling differentiation from draw_mtext, so it is adequate but not complete.

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 all meaning must come from the description. It explains x/y/text, height (with units in mm and its fallback), and align's two values, but never mentions the layer parameter or its default, leaving one of six parameters completely undocumented.

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 states a concrete action and resource: placing text at a point (x,y), including the font (Arial with Cyrillic support). It is clearly distinguishable from arc/line/polygon drawing siblings, but it does not distinguish itself from draw_mtext, the obvious single-vs-multiline alternative.

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 only implied by the fact that a text string is required. The description does give one useful operational pointer, cross-referencing set_annotation_scale for the automatic height behavior, but it never states when to prefer this over draw_mtext or how layer selection interacts with the defaults.

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