Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add cable

add_cable

Add a multi-conductor cable between two connectors, mapping pins 1:1 by name/order or via explicit conductor pairs, with optional tag, gauge, length, and spec.

Instructions

Add a multi-conductor cable between two connectors, e.g. from "B1:X1" to "IO1:X2". Pins are mapped 1:1 (same pin names, else pin order) unless conductors are given. Tag defaults to the next free W1, W2…

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": {
      "project_id": "<project_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "add_cable"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes"TAG:CONNECTOR"
tagNo
fromYes"TAG:CONNECTOR"
specNoPrinted on the bundle, e.g. "4×0.34 PUR 5m"
gaugeNoDefault gauge for its conductors. Wire gauge: AWG ("18", "14 AWG", "1/0") or mm² ("1.5 mm²"). A bare number follows the project's gauge units. Default: the signal type's gauge.
lengthNoCable length in the project's length unit (ft default, or m; update_project length_unit). Its conductors inherit it. null = unset.
conductorsNoExplicit pin map instead of 1:1
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral defaults that annotations do not convey: 1:1 pin mapping by name then by order, and auto-assignment of the next free W1/W2 tag. It says nothing about prerequisites (must the connectors exist?), whether pins or terminals are created as a side effect, or how tag collisions are handled.

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?

Three tightly packed sentences with the resource and example front-loaded and no filler. The inline example slightly duplicates the schema's "TAG:CONNECTOR" hint, but it is short and aids fast parsing.

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?

For an 8-parameter creation tool with no output schema, the description covers defaults but not outcomes: it does not say what is returned (e.g. the created cable tag), whether the connectors must pre-exist, or what error behavior to expect. Adequate to invoke, incomplete for an agent that must verify or recover from the call.

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?

With 75% schema coverage the baseline is 3, and the description earns above that. It supplies semantics for the undocumented tag parameter (defaults to next free W1, W2…) and clarifies when the conductors parameter overrides default pin mapping, which is the key behavioral parameter of this tool.

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 states a specific verb and resource ("Add a multi-conductor cable between two connectors") and gives a concrete identifier example ("B1:X1" to "IO1:X2"), so an agent knows exactly what object is created. It does not explicitly contrast itself with siblings like add_connections or add_terminal_strip, so the cable-vs-single-wire distinction is left implicit.

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 use case (bundling a cable between two connectors) is implied by the described default pin mapping, giving the agent enough to recognize a fit. However, there is no explicit when-to-use or when-not-to-use guidance, and no named alternative for cases where the agent should instead add individual wires or connections.

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