Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Split terminal strips by subsystem / function

split_strips

Split terminal strips so each serves one subsystem or function (power, PE, AC, field I/O per module), moving wires with their terminals. Reports the plan by default before applying.

Instructions

Split strips so each serves one subsystem and/or one function: power (TB-PWR), PE (TB-PE), AC (TB-AC), field I/O per PLC module (TB-IO); the rest stays on plain TB strips. Everything tied together on a strip moves as one unit; a unit serving several subsystems goes to their common parent (shared distribution at the level above). Wires move with their terminals; device connections never change. apply=false (default) reports the plan; ask the user before applying. pack=true also re-packs the results (like optimize_strips).

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

Input Schema

NameRequiredDescriptionDefault
byNoboth
packNo
applyNo
stripNoStrip tag; omit for every strip
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnly=false, destructive=false, and openWorld=false; the description adds genuinely new behavior beyond them – a plan-only default mode, the invariant that wires move with terminals and device connections never change, and the unit-cohesion rule for cross-subsystem units. It does not say whether a split can be undone or what the reported plan looks like, so it stops short of full disclosure.

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?

The rule set is front-loaded in the first sentence and each following sentence adds distinct information (unit cohesion, wire invariant, apply workflow, pack option). It is dense with domain shorthand (TB-PWR, TB-IO), which trades readability for precision but is not padded.

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?

No output schema and a non-trivial project-mutating transformation, yet the definition covers the decision rules, the default dry-run, the confirmation requirement, and what is preserved. Missing only reversibility/undo notes and any hint about the returned plan, which keeps it below top marks.

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?

Schema description coverage is only 20%, so the description carries the burden, and it does: 'by' is explained via the subsystem/function split, 'pack' via re-packing like optimize_strips, and 'apply' via plan-vs-execute with a user-confirmation requirement. Only 'strip' (documented in the schema) and the self-evident project_id are left unaddressed.

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 states a specific verb and resource (split strips) plus the exact partitioning rule: one subsystem and/or one function per strip, with concrete strip-name conventions (TB-PWR, TB-PE, TB-AC, TB-IO) and the fallback case (the rest stays on plain TB strips). It is clearly distinguishable from packing/optimization and from the add/remove strip siblings.

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?

It gives a concrete operating workflow: apply=false (default) only reports the plan, ask the user before applying, and pack=true re-packs like optimize_strips. That is clear context for safe invocation, but it does not explicitly say when to run this versus leaving strips alone or when a split is unnecessary.

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