Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

drawing_summary

Summarizes a drawing by reporting its file name and object counts by type using ezdxf, so you can inspect the drawing contents without manual counting.

Instructions

Сводка по чертежу: файл, число объектов (по типам в ezdxf).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/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, and it does disclose the substance of the behavior: a summary containing the file name and per-type object counts computed via ezdxf. It does not say whether the summary applies to the active drawing, whether it requires an open document, or whether it is cheap to call; those gaps are real but the core behavior is not hidden.

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?

One short sentence, front-loaded with the resource ('Сводка по чертежу') and followed by the payload contents. Nothing is redundant, though the parenthetical ezdxf detail is terse enough to be slightly cryptic to a reader unfamiliar with the library.

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 with zero parameters the input side is trivial. The remaining gap is scope and prerequisites: the description never says the summary describes the currently open drawing or what happens if none is open, which is the main thing an agent needs before calling.

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 tool takes zero parameters, so the baseline is 4 and there is no schema semantics for the description to add or omit. It correctly implies the target is implicit (the current drawing) rather than accepting a file argument.

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 states a specific resource and output content: a drawing summary with the file and object counts broken down by type via ezdxf. That is clearly more than a restatement of the name. It does not, however, distinguish this from a similarly scoped sibling such as acad_status, so an agent cannot tell from the text alone which of the two reports drawing state.

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 call this versus alternatives, nor any prerequisite or exclusion. The agent must infer that it is a read-only inspection call on the currently open drawing. Nothing routes it away from acad_status or the draw_* tools.

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