Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

cabinet_rails

Assign devices to specific DIN rails in top-to-bottom, left-to-right order, or clear the arrangement to return to automatic filling.

Instructions

Fix which devices go on each DIN rail, top to bottom, left to right (e.g. [["-QB1","-FC1"], ["-KF1","-TB1"]]). An empty list returns to automatic filling.

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": {
      "rails": "<rails>"
    },
    "name": "cabinet_rails"
  }
}

Input Schema

NameRequiredDescriptionDefault
railsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive mutation with openWorldHint=false, so safety is covered; the description adds genuinely useful behavior beyond that by disclosing the reset semantics of an empty list and the ordering convention applied to each rail. It does not say whether devices omitted from the lists are unassigned, whether invalid device tags error out, or whether the call replaces prior rail assignments wholesale. Note a mild tension: a 'fix the arrangement' set-operation is intrinsically repeatable, yet idempotentHint is false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences: the action and ordering rule first, an inline example immediately after, then the empty-list edge case. Nothing is redundant or buried, and the example substitutes for several sentences of schema prose.

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, return values need not be described, and the description covers action, ordering, input shape, and the reset case for this single-parameter mutation. Remaining gaps are around failure modes and partial-listing behavior, which are minor but would matter to an agent authoring a full rail layout.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single 'rails' parameter is only typed as array-of-array-of-string, so the description must carry the meaning—and it does, via the worked example showing one inner list per rail and the ordering of entries within each. It still doesn't clarify whether entries are device tags versus names, or whether rail order in the outer list maps to rail position/index.

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?

A specific verb and resource: it fixes device-to-DIN-rail assignment, with ordering stated ('top to bottom, left to right') and a concrete example of the nested-list shape. It is clearly a rail-configuration operation rather than a placement/geometry tool, though it doesn't explicitly name which sibling (cabinet_place, cabinet_configure) it supersedes for rail assignment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'empty list returns to automatic filling' line gives a usable reset case and implies the tool is used when manual rail ordering is needed instead of auto-fill. But there is no explicit statement of when to prefer this over cabinet_place or cabinet_configure, and no stated prerequisites (e.g., devices must already exist / be placed) before calling it.

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