Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

sheet_remove

Destructive

Deletes a sheet definition using its sheet ID to remove unwanted sheets from electrical documentation.

Instructions

Delete a sheet definition.

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

Input Schema

NameRequiredDescriptionDefault
sheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say what is lost (contents, devices, network links on the sheet), whether the operation is reversible, or whether dependent objects block deletion. For a destructive tool, this is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is efficient, but the brevity reflects under-specification rather than disciplined conciseness. Nothing is wasted, yet almost nothing is said.

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 need not be explained, but for a destructive single-parameter tool the definition leaves critical things unsaid: the meaning of sheet_id, side effects on dependent objects, and irreversibility. An agent could call it but could not call it confidently.

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?

Schema description coverage is 0%, so the single required parameter sheet_id is documented nowhere. The description never mentions the parameter or explains what identifier it expects (internal ID vs. name/path), so it fails to compensate for the coverage gap.

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 and resource ("Delete a sheet definition"), which is distinguishable from siblings like sheet_add, sheet_get, and sheet_update. It stops short of naming an alternative or clarifying whether the whole sheet or only its definition/metadata is removed, so it is clear but not fully disambiguated.

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 when-to-use guidance, no preconditions, and no pointer to alternatives such as sheet_update for modification versus deletion. The agent must infer entirely from the verb.

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