Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

network_unlink

Destructive

Remove network links between two specified devices to disconnect their electrical or industrial network connection.

Instructions

Remove the link(s) between two devices.

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": {
      "a_device": "<a_device>",
      "b_device": "<b_device>"
    },
    "name": "network_unlink"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_deviceYes
b_deviceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, and the description adds nothing on top of that — it only restates removal. It does not say what happens if no link exists (relevant given non-idempotency), whether the effect is immediate or reversible, or whether permissions are 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 front-loaded sentence with no padding or redundancy. It is efficient, though its brevity leaves little structure to build on.

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, non-idempotent mutation the description should cover at least the no-link-exists case and the format of the two device references. Those gaps leave an agent under-informed before calling.

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% with two required parameters, so the description must carry the load, yet it only implies that a_device and b_device are the two endpoints. It does not clarify expected identifier format (name vs. ID), whether the pair is order-sensitive, or what strings are accepted.

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 concrete verb ('Remove') and resource ('the link(s) between two devices'), which is enough to distinguish it from the inverse sibling network_link. It stops short of naming the complementary tool explicitly, so sibling differentiation is suggested rather than spelled out.

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 or when-not-to-use guidance, no mention of prerequisites such as the link already existing, and no reference to network_link as the way to create one. Usage must be inferred 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.