Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

transform_entities

Move, copy, rotate, scale, or mirror AutoCAD entities by handle or layer/type/area filters, returning new handles for edited or copied objects.

Instructions

Преобразовать объекты (handles или фильтр layer/entity_type/area). op: move (dx,dy), copy (dx,dy), rotate (angle° вокруг base_x,base_y), scale (factor от base), mirror (ось axis=[x1,y1,x2,y2]). copy=True: оставить исходные и изменить копии. Возвращает handle новых объектов.

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": {
      "op": "<op>"
    },
    "name": "transform_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxNo
dyNo
opYes
areaNo
axisNo
copyNo
angleNo
layerNo
base_xNo
base_yNo
factorNo
handlesNo
entity_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose key mutation semantics: copy=True keeps the originals and modifies copies, implying copy=False destructively alters the originals, which is important for a write tool. It also states that handles of the new objects are returned. Gaps remain on error behavior, permissions, and undo/reversibility.

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?

Purpose and target selection are front-loaded, then the operation-to-parameter mapping is packed into a single dense run. The telegraphic, abbreviated style ('scale (factor от base)') leaves no wasted words but is close to the edge of readability.

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 13-parameter mutation tool with no annotations, the description covers the operation set, target selection, copy semantics, and parameter mapping, and the existing output schema relieves it of explaining return values. The remaining shortfalls are the unspecified 'area' format and entity_type vocabulary.

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 description coverage is 0%, yet the description maps nearly every parameter to an operation (dx/dy for move/copy, angle around base_x/base_y for rotate, factor from base for scale, axis=[x1,y1,x2,y2] for mirror, copy, handles vs. the layer/entity_type/area filter). It adds substantial meaning beyond the bare titles, though it never specifies the 'area' array format or valid entity_type values, and op's allowed values are given only in prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Преобразовать объекты') plus the two ways of selecting targets (handles or a layer/entity_type/area filter) and enumerates the five supported operations. An agent can tell this apart from drawing, erasing, or listing siblings without opening the schema.

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: it shows how to target objects but never says when to prefer handles over filters, or when to use this tool versus erase_entities/array_entities. No explicit when-not guidance or prerequisites are given.

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