Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

block_insert

Insert an existing named block at a WCS point with XY scale and rotation, optionally assigning a layer. Places a single block reference in the active space.

Instructions

Insert an existing named block at a WCS point with XY scale and rotation in degrees, optionally assigning the new reference to a layer.

Side-effects: Adds INSERT entity to active space. Disambiguation: Inserts instance of existing block; use batch_insert_blocks for bulk placement.

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": "block_insert"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesInsertion point X coordinate in WCS
yYesInsertion point Y coordinate in WCS
nameYesName of existing block definition to insert
layerNoTarget layer for the block reference. Uses active layer if omitted
scale_xNoX scale multiplier (default: 1.0)
scale_yNoY scale multiplier (default: 1.0)
rotationNoInsertion rotation angle in degrees (default: 0.0)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • addedInput schema / properties / layer / description
      Added value: +"Target layer for the block reference. Uses active layer if omitted"
    • addedInput schema / properties / name / description
      Added value: +"Name of existing block definition to insert"
    • addedInput schema / properties / rotation / description
      Added value: +"Insertion rotation angle in degrees (default: 0.0)"
    • addedInput schema / properties / scale_x / description
      Added value: +"X scale multiplier (default: 1.0)"
    • addedInput schema / properties / scale_y / description
      Added value: +"Y scale multiplier (default: 1.0)"
    • addedInput schema / properties / x / description
      Added value: +"Insertion point X coordinate in WCS"
    • addedInput schema / properties / y / description
      Added value: +"Insertion point Y coordinate in WCS"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With only readOnlyHint=false for annotations, the description usefully discloses the side-effect (adds an INSERT entity to active space) and the default-layer fallback. It does not mention transaction/undo interaction or failure modes for a missing block definition, so it is strong but not exhaustive.

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?

Three labeled lines – core action first, then Side-effects and Disambiguation. Every sentence carries distinct information and nothing is repeated.

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?

Output schema exists, so return values need no explanation, and the mutation semantics plus sibling routing are covered. Missing only error/validation behavior (e.g., nonexistent block name) to be fully complete for a write tool.

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

Parameters3/5

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

Schema coverage is 100%, so all seven parameters are already documented, including units and defaults. The description restates rotation in degrees and XY scale but adds no syntax or constraint detail beyond the schema, so baseline 3 applies.

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 (Insert), resource (existing named block), and key parameters (WCS point, XY scale, rotation in degrees, optional layer). It is immediately distinguishable from batch_insert_blocks and from block_create/block_list siblings.

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?

Explicitly routes the agent: 'use batch_insert_blocks for bulk placement' names both the alternative and the selecting condition. It does not cover prerequisites such as the block needing to already exist in the drawing, but the usage context is clear.

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

Deploy Server

Other Tools