Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

set_annotation_scale

Sets annotation text height in millimeters for all dimensions and labels, letting you match drawing scale and readability; use 0 for automatic sizing.

Instructions

Масштаб надписей: высота текста размеров и подписей в мм для всего чертежа. Для планов зданий задайте крупно (500-1000 мм), для окон 80-120. 0 = авто (≈1/60 габарита, не меньше 80 мм).

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": {
      "text_height": "<text_height>"
    },
    "name": "set_annotation_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
text_heightYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses global scope ("для всего чертежа"), units in mm, and the special 0 = auto behavior with an approximation formula and minimum. It does not clarify whether existing annotations are modified, whether the change is reversible, or any permission/constraint details.

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 short and front-loaded: it states the effect first, then practical value guidance, then the special 0 behavior. Every phrase adds useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter setter with an output schema and no annotations, the description covers purpose, parameter meaning, global scope, and automatic behavior. The main remaining gap is whether it changes existing annotations globally or only sets future annotation sizing.

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 define the single parameter. It does so thoroughly: text_height is the height in mm, with practical ranges for plans and windows, plus the special value 0 meaning automatic scaling with a stated formula and minimum.

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 specific resource and effect: annotation/label scale, expressed as text height in mm for the entire drawing. It is clear what the tool sets, but it does not distinguish itself from sibling setters such as set_properties or set_layer.

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?

It gives context-specific value recommendations for building plans (500-1000 mm) and windows (80-120 mm), which implies when those values are appropriate. However, it does not say when to use this tool instead of related setters or what alternatives exist.

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