Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

terminals_assign_io

Routes each field-mounted I/O device to its own terminal on a specified strip and lists the assignment in the terminal plan for clear wiring documentation.

Instructions

Route every field-mounted I/O device through its own terminal on strip (drawn on the I/O sheets and listed in the terminal plan).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "terminals_assign_io"
  }
}

Input Schema

NameRequiredDescriptionDefault
plcNo
stripNo
descriptionNoSeñales de campo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already disclose a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the bar is lower. The description usefully adds that the operation is exhaustive ('every field-mounted I/O device') and that it produces drawing content on the I/O sheets plus entries in the terminal plan, but it omits what happens on re-run, whether existing terminals are overwritten, and what is required for the strip to exist.

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?

A single front-loaded sentence with the key target (`strip`) stated up front and no filler. The parenthetical is dense but earns its place by naming the outputs; slightly more clarity on the object of 'route' would help.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the return shape need not be described, and annotations cover safety semantics. What remains missing is prerequisite state (does `strip` need to exist, does `plc` constrain scope) and idempotency behavior — real gaps for a bulk mutation, but not fatal.

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% across three parameters, so the description must carry parameter meaning, yet it only explains `strip` and only obliquely (the target terminal strip). The `plc` scoping parameter and the `description` field — which defaults to a Spanish label and likely becomes the annotation text — are entirely undiscussed, leaving an agent unsure whether `plc` limits the scope of 'every device'.

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 gives a concrete verb and object: route every field-mounted I/O device to its own terminal on a named strip. It also hints at the artifact scope (I/O sheets, terminal plan), but it never distinguishes itself from likely neighbors such as terminals_add or plc_io_assign, so an agent must guess which tool performs the bulk vs. single-terminal operation.

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 prerequisites, and no named alternative. The agent is left to infer that this is the bulk-assignment variant and that single-terminal work belongs elsewhere.

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