Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

list_blocks

Lists drawing blocks with attribute tags and insertion counts; enable include_inserts to retrieve each block insertion's handle and attribute values.

Instructions

Список блоков (теги атрибутов, число вставок). include_inserts=True: вставки с handle и значениями атрибутов.

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

Input Schema

NameRequiredDescriptionDefault
include_insertsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the conditional behavior of the flag (inserts returned with handle and attribute values) and the shape of the listing, but says nothing about read-only nature, prerequisites, or scale/pagination behavior of large block tables.

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?

Two short, front-loaded clauses with zero filler: the resource and contents first, then the flag behavior. Nothing could be removed without losing meaning.

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 spelled out, and the single optional parameter is explained. However, the definition omits surrounding context an agent needs, such as whether a drawing must be active and how the result relates to list_entities or 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?

The single parameter has 0% schema description coverage, yet the description explains exactly what include_inserts=True adds (inserts with handles and attribute values), which is the key semantic gap. It only implicitly conveys the default (False) behavior of returning blocks without inserts.

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 (list blocks) and even names what the listing contains (attribute tags, insert count), so the agent knows this is not draw_* or create_block. It does not explicitly distinguish itself from the other list_* siblings (list_entities, list_layers, list_profiles), leaving the resource distinction to be inferred from the word 'blocks'.

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: the agent can infer 'call this to enumerate blocks' and 'set include_inserts to get inserts with handles and attribute values'. There is no explicit when-to-use/when-not-to-use statement and no mention of alternatives or prerequisites such as requiring an open drawing.

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