Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Update wire

update_connection

Change one existing wire by ID, updating endpoints, signal, gauge, note, draw mode, bundle tag, or length; omitted fields remain unchanged.

Instructions

Change one wire (grid row) by id: either end, signal, note, draw mode, gauge, bundle tag, or length (in the project's unit; null clears). Omitted fields stay the same; note "" clears it, gauge "" goes back to the signal type's gauge, bundle "" clears the tag.

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>",
      "connection_id": "<connection_id>"
    },
    "name": "update_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo"TAG:TERMINAL", e.g. "PLC_MAIN:24V"
drawNoauto (default), force a drawn wire, or force reference flags
fromNo"TAG:TERMINAL", e.g. "PSU1:+24V"
noteNo
gaugeNoWire 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.
bundleNoFree tag for loose wires that run together ("duct-1"), so their count derates ampacity. Ignored on cable conductors (the cable is the bundle).
lengthNoWire length in the project's length unit (ft default, or m; update_project length_unit), for the voltage-drop check. null clears it. Cable conductors inherit the cable's length.
signalNoSignal type name or id. Default: the From terminal's Codex signal.
project_idYes
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive, non-open-world mutation, so the description's job is to explain the mutation's shape — and it does: it is a partial update where unspecified fields are preserved, and empty strings/null have distinct clearing semantics. It stops short of describing permissions, error behavior, or whether the call returns the updated wire.

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 sentences, front-loaded with the action and the editable field list, followed by the default/clearing rules. Dense but every clause carries a rule; the only cost is that the second sentence packs four separate rules into one line.

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 a 10-parameter partial-update tool with no output schema, the definition covers the field set, the inheritance rules, and the clearing conventions. What is missing is only the response shape and failure modes, which are secondary for a correctly-scoped update 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 10 parameters at 70% schema coverage, the description meaningfully compensates: it spells out that "" resets gauge to the signal type's gauge and clears note/bundle, and that length is in the project's unit and null clears it. Those clearing rules are the non-obvious semantics an agent would otherwise guess wrong on.

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?

"Change one wire (grid row) by id" names a specific verb and resource and then enumerates exactly which fields can be changed (ends, signal, note, draw mode, gauge, bundle tag, length). The parenthetical "grid row" and the singular "wire" make it distinguishable from cable/harness siblings, though no sibling is named explicitly.

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 description gives strong usage rules for how to use the tool (omitted fields stay the same, "" clears a note or bundle, null clears length), but says nothing about when to choose this over update_cable or add_connections, nor any preconditions such as needing the connection to already exist.

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