Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

erase_entities

Deletes drawing objects by handle list or by layer, entity type, and area filters, supporting targeted removal of unwanted AutoCAD entities.

Instructions

Удалить объекты по списку handles или по фильтру (layer/entity_type/area).

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

Input Schema

NameRequiredDescriptionDefault
areaNo
layerNo
handlesNo
entity_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/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 for a destructive mutation, and it discloses essentially none of it: no mention of irreversibility or undo, no permissions/auth requirements, no note on what happens to entities not matching a filter, and no handling of conflicting handles+filter input.

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 sentence, front-loaded with the verb and resource, with the alternative modes enumerated in parentheses. Zero waste, though the extreme terseness is part of why key semantics are missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 needn't be explained, but for a destructive, four-parameter tool with no annotations and no schema descriptions, the description is too thin. It omits destructiveness/undo, filter combination logic, and precedence between the two modes — all of which an agent needs before calling it.

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?

Schema description coverage is 0%, so the description must compensate; it does name all four parameters and groups them into two selection modes. However, it adds no format detail (handle string form, area's coordinate layout), no rule for how layer/entity_type/area combine (AND vs OR), and no statement that handles takes precedence.

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 ("Удалить" / delete) and resource ("объекты" / entities) plus the two supported selection modes (handles list or filter). It is clear what the tool does, though it never names or contrasts against read-side siblings like list_entities/select_entities, which a deleting agent would plausibly confuse.

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?

Implicitly conveys when to use which form: pass a handle list for known targets, or a filter for a batch. It gives no explicit when-not guidance, no statement of which mode wins if both are supplied, and no warning that this is an irreversible destructive action.

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