Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Update cable

update_cable

Change a cable by tag or ID to edit tag, spec, gauge, length, endpoints, pin map (reset or replace), or draw mode; omitted fields stay unchanged.

Instructions

Change a cable by tag or id: retag, spec, gauge, length, either end (the pin map resets to 1:1), replace the whole pin map (conductors), reset it (reset_pin_map), or set the draw mode. Omitted fields stay the same.

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>",
      "cable": "<cable>"
    },
    "name": "update_cable"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo"TAG:CONNECTOR"
drawNo
fromNo"TAG:CONNECTOR"
specNo"" clears it
cableYesCable tag (W1) or id
gaugeNoDefault gauge for its conductors; "" clears it. 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; its conductors inherit it. null clears it.
new_tagNo
conductorsNoReplaces the pin map
project_idYes
reset_pin_mapNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses important side effects the annotations do not: changing either end resets the pin map to 1:1, and conductors replaces the whole pin map. It also states the partial-update contract ("Omitted fields stay the same"). The pin-map reset is arguably a destructive side effect while destructiveHint=false, worth noting but not a direct contradiction.

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 that enumerates options compactly with zero filler. The dense parentheticals ("the pin map resets to 1:1", "reset_pin_map") are information-bearing, though the packing makes it slightly harder to scan than a short bulleted list would be.

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?

For an 11-parameter mutation tool with no output schema and only basic annotations, the description covers the primary semantics and the key side effects. Gaps remain around return values, permission requirements, and what happens when conflicting options (conductors + reset_pin_map + from/to) are combined, but the essential calling information is present.

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?

At 64% schema coverage, the description earns credit for mapping prose to parameters: retag→new_tag, replace pin map→conductors, reset_pin_map by name, and the from/to end semantics with their 1:1 reset consequence. It adds meaning the schema does not, notably the interaction between end changes and the pin map, though it does not clarify precedence when multiple mutating options are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Change a cable by tag or id") and then enumerates every mutable facet: retag, spec, gauge, length, ends, pin map, draw mode. An agent can immediately tell this is the partial-update tool for an existing cable, distinct from add_cable/remove_cable.

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?

Usage is implied rather than stated: the tool is for modifying an existing cable, and "Omitted fields stay the same" establishes partial-update semantics. However, it never explicitly says when to prefer this over siblings like add_cable or update_connection, nor does it state prerequisites or mutual-exclusion rules (e.g. conductors vs reset_pin_map vs from/to).

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