Power CAD MCP

by khs0927

Overview Schema Source Related Servers Discussions Admin

Hybrid

delete_layer

Destructive

Removes an unused layer from an AutoCAD drawing by name, helping keep CAD layers organized and avoid clutter.

Instructions

Delete an unused layer.

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

Name	Required	Description	Default
`name`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already mark this as destructive, non-read-only, non-idempotent, and closed-world, so the safety profile is covered. The description adds the 'unused' precondition, which is useful behavioral context, but it does not explain what happens if the layer is in use, whether deletion is reversible, or any failure modes. This is a modest addition beyond annotations.

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 description is a single front-loaded sentence with no wasted words. It is appropriately concise, though the extreme brevity leaves important context unstated for a destructive operation.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile. However, for a destructive tool with one undocumented parameter and many sibling layer operations, the description omits key prerequisites and side effects, such as whether a used or current layer can be deleted. It is not complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, name, and schema description coverage is 0%, meaning the description should compensate for missing parameter documentation. The description does not mention the name parameter, its expected format, or which layer it identifies, so it adds no meaning beyond the schema's bare property title.

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 clear verb and resource: delete a layer. It implies a constraint that the layer must be unused, which distinguishes it somewhat from create/update/list layer tools. However, it does not explicitly differentiate itself from delete_entities or explain the 'unused' condition, so it is not fully precise.

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?

The description offers no explicit guidance on when to use this tool versus alternatives such as update_layer or delete_entities. The word 'unused' hints at a precondition, but there is no statement of exclusions, prerequisites, or alternatives.

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