Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

create_block

Create a named AutoCAD block from selected objects or a construction, set its base point, optionally replace source objects with the block, and add attribute tags.

Instructions

Создать блок name из объектов (handles) или из конструкции (kind + params, как в draw_construction). base_x/base_y: базовая точка. replace=True: исходные объекты заменяются вставкой блока. attributes: список тегов атрибутов (например ['MARK','NOTE']).

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

Input Schema

NameRequiredDescriptionDefault
kindNo
nameYes
base_xNo
base_yNo
paramsNo
handlesNo
replaceNo
attributesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/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, and it does disclose the one destructive behavior: replace=True means source objects are swapped for the block insertion. It says nothing about overwriting an existing block of the same name, what happens if both handles and kind/params are supplied, or permission requirements — significant gaps for an 8-parameter mutation 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?

Front-loaded with the core action, then param-by-param clauses in schema order; no filler sentences. It is terse to the point of near-telegraphic phrasing, which slightly raises parsing effort but wastes nothing.

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?

Return values are covered by the output schema, so their absence is fine, and the destructive replace flag is disclosed. For an 8-parameter, unannotated creation tool, the missing mode-conflict rules, name-collision behavior, and attribute semantics leave real ambiguity.

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 compensate, and it touches all eight parameters: name, handles, kind, params, base_x/base_y, replace, and attributes, including a concrete example value for attributes. Depth is thin for kind/params, which are delegated to 'as in draw_construction', but the overall mapping is complete.

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?

States a specific verb and resource (create a block named name) and distinguishes two input modes: from existing objects via handles, or from a construction via kind + params. It does not explicitly contrast with the sibling insert_block, so the boundary between creating a definition and inserting one is left to the agent.

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?

It implicitly tells the agent which argument path to take (handles for existing geometry, kind + params for a parametric construction, with draw_construction as the reference for those values). There is no explicit when-to-use versus insert_block, no statement on whether the two modes are mutually exclusive, and no prerequisites or name-collision guidance.

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