Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

array_entities

Copies selected AutoCAD objects into rectangular or polar arrays using handles or layer/type/area filters; originals stay unchanged.

Instructions

МАССИВ копий объектов (handles или фильтр layer/entity_type/area). mode='rect': rows×cols с шагом dx, dy (исходник в левом нижнем углу). mode='polar': count копий по кругу вокруг (cx,cy) на угол angle (360 = полный круг), rotate_items=False: копии не поворачиваются. Исходные объекты остаются.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "array_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
cxNo
cyNo
dxNo
dyNo
areaNo
colsNo
modeNorect
rowsNo
angleNo
countNo
layerNo
handlesNo
entity_typeNo
rotate_itemsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/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. It does disclose the important non-destructiveness fact ("Исходные объекты остаются") and the rotate_items=False semantics, but says nothing about what happens when neither handles nor any filter is supplied, nor about permissions or failure modes. Solid but incomplete for a mutating tool.

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?

Dense and front-loaded: the mode-specific parameter groupings are stated in compact clauses with no filler. Readability suffers slightly from run-on parentheticals and would improve with explicit per-mode structure.

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 14-parameter tool with an output schema and no annotations, the description covers modes, geometry, item rotation, and source preservation — enough to invoke it correctly. The main omissions are default behavior (empty handles + no filters) and the area parameter's format.

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%, so the description must do the work — and it defines nearly all 14 parameters: rows, cols, dx, dy, cx, cy, count, angle, mode, rotate_items, and the handles/layer/entity_type/area selector set. The remaining gap is the 'area' parameter, whose expected format (e.g. box coordinates) is never explained.

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?

Opens with a specific verb+resource ("МАССИВ копий объектов") and immediately names the two input routes (explicit handles or a layer/entity_type/area filter) plus the two modes. An agent can tell this creates copies rather than modifying originals. It doesn't explicitly distinguish itself from siblings such as transform_entities, so it falls short of a 5.

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

Usage Guidelines4/5

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

Gives concrete mode-selection guidance: mode='rect' with rows/cols/dx/dy, mode='polar' with count/cx/cy/angle, and the 360-degree convention. No explicit when-not-to-use or named alternative tool appears, which keeps it below 5.

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