Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

terminals_remove

Destructive

Remove one terminal from the electrical documentation by providing its reference, such as '-XD2:5'.

Instructions

Remove one terminal, e.g. '-XD2:5'.

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

Input Schema

NameRequiredDescriptionDefault
refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/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 the reference format but says nothing about whether removal is permanent, what happens to dependent I/O assignments, or whether confirmation is required.

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 short sentence with the action front-loaded and no wasted wording. It is efficient, though the brevity contributes to the missing behavioral and usage context.

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 described, and annotations handle the destructive nature. However, for a destructive mutation with an undocumented required parameter, the description leaves the identifier semantics and side effects on related I/O assignments unspecified.

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?

The single `ref` parameter has 0% schema description coverage, so the description must compensate. The example '-XD2:5' usefully illustrates the expected string form, but it does not explain whether this is a terminal label, a sheet-qualified identifier, or how to discover valid values.

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 ('Remove one terminal') and gives an example reference ('-XD2:5'), so the operation is unambiguous. It does not explicitly distinguish itself from the sibling terminals_add, leaving that inference to the reader.

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 guidance on when to use this tool versus alternatives such as terminals_add or the other *_remove tools. No preconditions, ordering constraints, or exclusions are stated.

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