Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Update components

update_components

Retag components, relink parts, assign subsystems, place I/O modules in PLC slots, or set fuse and breaker trip ratings. Identify each component by its current tag.

Instructions

Retag a component, relink it to another Codex part, move it into a subsystem (subsystem: name/id, or "" for top level), put an I/O module in a PLC slot (plc + slot; a module already in that slot is taken out), or set a fuse/breaker's trip rating (trip_a; must be one of the part's allowed ratings when it lists any). Identify by current 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>",
      "changes": "<changes>"
    },
    "name": "update_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/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 supplied. The description earns credit for disclosing a real side effect beyond the annotations — 'a module already in that slot is taken out' — and a validation constraint ('must be one of the part's allowed ratings when it lists any'). It says nothing about batch atomicity, partial failure, or what happens when a given tag is not found, which matters for a mutation tool taking an array.

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 opens with the operations and closes with the addressing rule, with zero filler. It is dense with parentheticals and reads as a run-on, which slightly raises parsing cost, but no clause is dispensable.

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?

With no output schema and no annotations covering outcomes, the description is silent on the return value, on whether a multi-item changes array applies all-or-nothing, and on the error surface for unknown tags or disallowed ratings. The operation semantics are complete, but the operational contract for a batch mutation is not.

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?

Top-level schema coverage is 0% and the two required parameters are undocumented, so the description must carry the load. It does: it explains the semantics of subsystem ("" = top level), the plc+slot pairing and displacement rule, and the trip_a allowed-ratings constraint, and pins identity to 'current tag' (implying new_tag is the change). It omits trip_a_by_terminal and part_id, both of which appear only in the nested schema.

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 names a specific verb set on a specific resource (retag, relink, re-subsystem, place in PLC slot, set trip rating on a component) and identifies the addressing key ('Identify by current tag'). It is clearly the mutate-in-place counterpart to the add_/remove_component siblings, so an agent can distinguish it without opening the schema.

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?

Each supported operation is enumerated with the fields that select it (subsystem for relocation, plc+slot for I/O modules, trip_a for fuses/breakers), which gives clear per-mode usage context. It stops short of stating when to prefer this over remove_components + add_components, or what to do when a tag is unknown.

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