Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

add_leader

Creates AutoCAD leader or multileader annotations with multiline text, using point coordinates to place the arrow tip and text. Set optional text height.

Instructions

Выноска (мультивыноска) с текстом: points [[x,y] остриё стрелки, ..., [x,y] где текст]. Текст можно в несколько строк через \n.

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>",
      "text": "<text>"
    },
    "name": "add_leader"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
pointsYes
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It explains leader geometry and text placement, but never states that it creates a new drawing entity, which layer is affected, or what side effects the operation has.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no filler. The point-ordering and newline details are compact and directly useful.

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 returns need not be described. For a simple three-parameter add tool, the description covers the core geometry and multiline text, but with no annotations it omits mutation/side-effect context and does not explain text_height.

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?

With 0% schema description coverage, the description adds useful meaning for points (first [x,y] is arrow tip, last [x,y] is text anchor) and text (multiline via \n). It does not explain text_height and leaves intermediate points undefined, so compensation is only partial.

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 identifies the specific entity as a leader/multileader with text and clarifies point ordering (arrow tip to text location), so purpose is clear. It does not compare to siblings such as draw_mtext or add_dimension, so 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 Guidelines2/5

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

It gives no when-to-use or when-not-to-use guidance and names no alternatives. The multiline text note explains parameter format, not usage context.

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