Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

network_link

Connect device ports with protocol, cable, and length details to draw a PLC-rooted network tree for electrical documentation.

Instructions

Connect device ports: [{a_device, a_port, b_device, b_port, protocol: profinet|ethernet|iolink, cable?, length_m?}]. The network sheet draws them as a tree rooted at the PLC.

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": {
      "links": "<links>"
    },
    "name": "network_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false), so the bar is lower. The description does add real context beyond them by noting the network sheet renders links as a tree rooted at the PLC, which tells the agent this is a persistent, visualized mutation. It says nothing about duplicate-link handling or failure when a device/port is unknown.

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?

Two short sentences, the payload is front-loaded and the behavioral note follows. The inline pseudo-schema notation is terse but readable; nothing is padded.

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 carry the safety profile. Still, for a batch mutation taking an array of links, the definition leaves open conflict/duplicate behavior and whether referenced devices and ports are validated.

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?

Schema description coverage is 0%, so the description must compensate: it lists the link fields and marks cable and length_m as optional, which adds meaning. But it omits required-field status (a_device/b_device), the a_port/b_port empty-string defaults, the length_m > 0 constraint, and it lists the protocol enum as profinet|ethernet|iolink while the schema also permits profisafe — an incomplete enumeration.

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: 'Connect device ports', with the payload shape spelled out. An agent can tell this is the create-side counterpart to network_unlink/network_list, though the description never names those siblings explicitly.

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 explicit when-to-use or when-not-to-use guidance, no mention of prerequisites (devices must already exist), and no pointer to network_unlink for the inverse operation. Usage is only implied by the verb 'Connect'.

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