Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

plc_io_remove

Destructive

Removes a single PLC I/O channel assignment by PLC and address, letting you delete outdated or incorrect channel mappings from electrical documentation.

Instructions

Remove one I/O channel assignment.

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": {
      "plc": "<plc>",
      "address": "<address>"
    },
    "name": "plc_io_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
plcYes
addressYes

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 openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not say whether the removal fails on an unknown assignment, whether it cascades to linked terminals or signals, or whether confirmation is required for a destructive non-idempotent operation.

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?

A single short sentence with no wasted words and the action front-loaded, but its brevity comes at the cost of under-specification rather than true efficiency. There is no structure beyond one clause.

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?

For a destructive, non-idempotent mutation with two undocumented parameters, the definition should at minimum explain the address format and failure behavior. An output schema exists so return values need not be explained, but the input and behavioral gaps leave it insufficient for this complexity.

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%: neither 'plc' nor 'address' carries any description, and the description text adds no meaning about the expected format (e.g. PLC identifier string, I/O address notation) or whether the address must match an existing assignment. With full burden on the description and nothing supplied, this is a clear 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 (remove) and a specific resource (one I/O channel assignment), which cleanly separates it from plc_io_assign and plc_io_list without naming them. It stops short of explicitly routing the agent away from siblings, so it is clear but not fully differentiated.

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 versus plc_io_assign, terminals_remove, or device_remove, and no stated preconditions such as whether the assignment must exist or whether other objects depend on it. The agent must infer usage purely from the verb.

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