Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

potential_set

Declare a rail potential with name and kind to assign the correct conductor color on drawings and lists.

Instructions

Declare a potential (rail): e.g. name='24V' kind='dc_plus', or 'L1_CTRL' kind='ac_control'.

The kind decides the conductor colour on drawings and lists.

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": {
      "name": "<name>",
      "kind": "<kind>"
    },
    "name": "potential_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
sourceNo
voltageNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent, closed-world mutation, so the safety bar is lower. The description adds genuinely useful behavior — the kind drives conductor colour on drawings and lists — but is silent on what happens if a name already exists, since idempotentHint=false leaves that ambiguous.

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, front-loaded with the action and examples, with zero filler. It is efficiently written but so terse that the compression is part of the under-specification problem rather than purely a virtue.

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?

Because an output schema exists, return values need no explanation. However, for a mutation with two wholly undocumented parameters and no stated behavior on duplicate names, the definition does not fully cover what an agent needs to invoke it confidently.

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%, so the description carries the full burden, yet it only addresses two of four parameters. It illustrates name conventions ('24V', 'L1_CTRL') and explains the consequence of kind, but 'source' and 'voltage' are never defined anywhere.

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 ('Declare a potential (rail)') and immediately grounds it with two concrete examples showing the name/kind pairing. The purpose is unmistakable; there is no sibling doing potentials, so no differentiation is required, though the description never says so 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 when-to-use, when-not-to-use, or prerequisite guidance at all, such as whether a potential must exist before network_link or plc_io_assign, or whether the project must be open. Usage can only be inferred from the two examples.

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