AutoCAD MCP

autocad_list_block_attributes

Read-onlyIdempotent

List attribute tags and values for a block reference by handle to inspect or validate AutoCAD block data.

Instructions

List the attribute tags/values on a block reference.

Args: params (ListBlockAttributesInput): - handle (str): handle of a block reference (INSERT entity).

Returns: str: JSON {"handle", "block", "attributes": [{"tag", "value"}, ...]}.

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": {
      "params": "<params>"
    },
    "name": "autocad_list_block_attributes"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered by structured fields. The description's main addition is the return shape, which duplicates the existing output schema, and it says nothing about behavior when the block has no attributes or a bad handle is supplied.

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?

The purpose is front-loaded in one clean sentence, and the Args/Returns blocks are compact. The Returns section is somewhat redundant given an output schema exists, slightly diluting conciseness.

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 simple one-argument read tool with full annotations, a return description and a published output schema, the definition covers what an agent needs to invoke it correctly. Only edge-case behavior (missing attributes, invalid handle) is unaddressed.

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?

With a single parameter and low reported schema coverage, the description restates the parameter as a 'handle of a block reference (INSERT entity)'. That INSERT-entity qualification adds real meaning, but the rationale, hex format and provenance of the handle are largely left to the schema and the Args block reads close to a restatement.

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 first sentence gives a specific verb (List) and resource (attribute tags/values) scoped to a block reference, so an agent immediately knows this is a read of INSERT attributes rather than a mutation. It stops short of naming the sibling autocad_set_block_attribute explicitly, which would have pushed it to a 5.

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 handle is described as 'handle of a block reference (INSERT entity)', which signals the tool operates on block references. There is no statement of when to prefer this over autocad_get_entity or autocad_query_entities, and no preconditions are given.

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

Deploy Server