Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

terminals_add

Add terminals to an electrical strip, creating it if missing; specify count or explicit numbers, and mark protective-earth terminals with pe=true.

Instructions

Add terminals to a strip (created when missing; tag auto -XD1.. if omitted). Either count consecutive numbers or explicit numbers. Mark protective-earth terminals with pe=true.

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_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
peNo
countNo
stripNo
numbersNo
potentialNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds meaningful context beyond them by disclosing an implicit side effect (strip creation when missing) and the auto-tagging rule (-XD1..). It does not say what happens on duplicate numbers, whether repeated calls stack terminals, or what errors look like for a non-idempotent write.

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 sentences, front-loaded with the action and the creation side effect, with parentheticals carrying the tag convention and pe semantics. No filler, nothing repeated from the schema titles.

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 no explanation. However, for a non-idempotent mutation with 0% schema documentation, the description leaves gaps: behavior on duplicate terminal numbers, the meaning of `potential`, and whether the strip is auto-committed or requires a later build step.

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% across 6 parameters, so the description must compensate. It meaningfully explains `count`, `numbers`, `pe`, and the `strip` creation behavior, but says nothing about `potential` or `description`, leaving two parameters entirely undefined for the agent.

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+resource ('Add terminals to a strip') and immediately qualifies the two operating modes (count vs. explicit numbers) plus the pe flag. It does not explicitly differentiate from siblings like terminals_remove or terminals_assign_io, but the action is unambiguous.

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

Usage Guidelines4/5

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

Explains the two mutually alternative input modes ('Either `count` consecutive numbers or explicit `numbers`') and that a strip is created when missing, which is real selection guidance. It stops short of naming alternatives or when-not-to-use conditions.

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