Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

insert_block

Places a named or file-based block into an AutoCAD drawing at specified coordinates, with optional scale, rotation, and attribute values.

Instructions

Вставить блок: name (или путь к .dwg в COM / .dxf в ezdxf), точка (x,y), scale, rotation°, attributes: {ТЕГ: значение}.

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": {
      "name": "<name>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "insert_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameYes
scaleNo
rotationNo
attributesNo

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 supplied, so the description carries the full behavioral burden. It signals a mutation and hints at backend differences (.dwg via COM vs .dxf via ezdxf), but says nothing about which space/layer the block lands in, what happens if the named block or file is missing, or whether existing entities are affected.

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?

A single terse sentence that front-loads the action and then lists operands in call order; no filler. It is arguably over-compressed, but nothing is redundant.

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 return values need not be described, and the parameter surface is reasonably covered. Still missing for a mutation tool with no annotations: target space/layer, error conditions, and the relationship to create_block.

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?

With 0% schema description coverage, the description does the compensating work: it clarifies that name accepts a block name or a .dwg/.dxf path, that x,y form a point, that rotation is in degrees, and that attributes is a TAG→value map. It omits the scale/rotation defaults and the fact that attribute values are strings, which the schema does carry.

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 and resource ('Вставить блок') and enumerates the operands (name, point, scale, rotation, attributes), so an agent can tell it inserts an existing block rather than creating one. It does not explicitly name create_block as the contrasting sibling, so it stops short of full differentiation.

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?

There is no statement of when to use this tool versus create_block, nor any precondition such as the block definition needing to exist or a drawing being active. Usage is only implied by the verb, leaving the agent to infer the create-vs-insert decision.

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