Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

purge

Remove unused empty layers, blocks, and styles from AutoCAD drawings to reduce clutter and file size.

Instructions

Очистить чертёж от неиспользуемого (PURGE): пустые слои, неиспользуемые блоки и стили.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the target set but says nothing about irreversibility, undo availability, whether in-use-but-referenced layers/blocks are spared or cascaded, or whether the operation can be previewed — critical omissions for a destructive cleanup.

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?

A single sentence, front-loaded with the action and immediately followed by the enumerated targets. No filler, no repetition of the tool name beyond the parenthetical PURGE anchor.

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 explained, and a zero-parameter tool is inherently simple. However, with no annotations the description should have flagged that this removes content permanently and whether it is undoable — that gap matters more than the missing return details.

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 the schema requires no elaboration. The description correctly implies a whole-drawing, all-or-nothing purge rather than a scoped one, which is the only parameter-like semantic relevant here.

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?

Names a specific verb and resource ('Очистить чертёж от неиспользуемого') and enumerates exactly what is removed: empty layers, unused blocks and styles, and ties it to the AutoCAD PURGE concept. It does not name the siblings it differs from (delete_layer, erase_entities), which keeps it short of 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 implied by the word 'неиспользуемого' — an agent can infer this is a cleanup/maintenance call rather than a modelling one. There is no explicit statement of when to call it, when not to, or what alternatives exist for removing entities that are in use.

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