Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

add_dimension_chain

Creates chained linear dimensions from ordered points along a horizontal or vertical line, with optional offset placement and an overall total dimension.

Instructions

ЦЕПОЧКА РАЗМЕРОВ по точкам [[x,y],...] (по порядку): соседние размеры на одной линии. direction: 'horizontal' (меряется по X) или 'vertical' (по Y). at: координата размерной линии (y для horizontal, x для vertical); без неё: на 3 высоты текста ниже/левее точек. total=True: общий размер дальше от объекта.

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

Input Schema

NameRequiredDescriptionDefault
atNo
totalNo
pointsYes
directionNohorizontal
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose real defaults: placement falls back to 3 text heights below/left of the points when 'at' is omitted, and total=True puts an overall dimension further from the object. It says nothing about which layer the dimensions land on, whether the call mutates/undoes prior geometry, or any failure conditions.

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?

Extremely dense and front-loaded: the core concept, point ordering, direction modes, default placement, and total behavior all land in a few telegraphic clauses with no filler. Nothing in it could be cut without losing a distinct fact.

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?

An output schema exists, so return values need no explanation, and the description covers the geometry semantics an agent needs to call it correctly. The only material gaps are the undocumented text_height parameter and the absence of any annotation substitute for a drawing-mutating tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the schema supplies only bare titles — so the description must compensate, and it does for 4 of 5 parameters: points format [[x,y],...] and ordering, direction's two accepted values with their measurement axis, at's coordinate meaning plus default, and total's effect. text_height is never mentioned, leaving one parameter undocumented in both places.

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 opens with a specific verb+resource in caps — a chain of dimensions built along a point list in order — which is clearly distinct from the single-dimension siblings (add_dimension, add_angular_dimension, add_radial_dimension). It never names those siblings explicitly, so differentiation is by implication rather than statement.

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 implied rather than stated: 'adjacent dimensions on one line, in point order' tells an agent the shape of the use case, and the direction semantics clarify the two modes. There is no explicit when-to-use vs add_dimension, no prerequisites, and no exclusions.

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