Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

delete_layer

Removes an empty layer from an AutoCAD drawing, excluding layer 0, Defpoints, and the current active layer.

Instructions

Удалить пустой слой (не 0, не Defpoints, не текущий).

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/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 does disclose meaningful restrictions (protected layers 0/Defpoints and the current layer are refused), which is real behavioral value, but it says nothing about irreversibility, error/failure responses, or permission requirements for a destructive operation.

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?

A single short sentence with the operation front-loaded and the constraints in parentheses — no waste. It is arguably too terse for a destructive operation, which is why it is not a 5.

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 the tool takes only one parameter. Still, for a destructive, non-annotated tool, the definition omits failure modes and irreversibility, and it is written in Russian while the tool name, title, and schema are English.

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?

There is one parameter ('name') with 0% schema description coverage, so the description must compensate. The word 'слой' (layer) implies the parameter is the layer name, but case sensitivity, accepted formats, and error behavior for unknown names are left unstated.

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 gives a specific verb and resource ('Удалить пустой слой' = delete an empty layer) plus scope qualifiers, so an agent knows exactly what the tool operates on. It does not name or distinguish itself from siblings such as erase_entities or set_layer, which keeps it from 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 through eligibility conditions: the layer must be empty and must not be '0', 'Defpoints', or the current layer. That is useful precondition guidance, but the description never states when to prefer this tool over alternatives (e.g., erase_entities) or what to do when the target fails these checks.

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