Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Optimize terminal strips

optimize_strips

Repack terminal strips into the fewest jumpered runs, removing empty spares and grouping like signals. Reports before/after counts first; applying renumbers unlocked terminals.

Instructions

Re-pack terminal strips to the fewest terminals: each net becomes one jumpered run sized to its wires (block capacity), empty spares go, like signals sit together, unlocked terminals are renumbered 1..n (locked ones keep their numbers). Multi-level and diode/LED blocks, cabled nets, and nets whose wires don't fit a run's clamp range (block wire_mm2) are left as they are. With spare_terminal_pct set (update_project), each packed strip ends with that share of its used terminals as empty spare terminals. Device connections never change. apply=false (default) only reports the before/after counts; ask the user before applying, since terminal numbers change.

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": "optimize_strips"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
stripNoStrip tag; omit for every strip
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses what is preserved (device connections, locked terminal numbers, multi-level/diode blocks, cabled nets, out-of-clamp-range nets) and what mutates when applying. The irreversibility warning about renumbering is exactly the kind of context destructiveHint=false cannot convey. Minor gap: the response for apply=true is never described.

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?

Front-loaded with the outcome first, then exceptions, then the safety guidance about apply. Dense and mostly earned, though a few clauses are packed into run-on sentences that could be split for scanability.

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 exists, and the description covers the report-only case (before/after counts) so an agent knows what apply=false returns. It does not describe the result shape when apply=true, and the parenthetical block-capacity/wire_mm2 details assume domain familiarity, leaving a small completeness gap for a mutating tool.

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 only 33% schema coverage, the description carries the burden and does explain apply (default false, report-only) and the strip targeting via the schema tag. It also references spare_terminal_pct, which is not a parameter of this tool (it belongs to update_project), which risks a small amount of confusion but is framed correctly as an update_project setting.

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?

States a specific verb and resource ("Re-pack terminal strips to the fewest terminals") and enumerates the concrete effects: nets merged into jumpered runs, spares removed, signals grouped, terminals renumbered. An agent can distinguish this from split_strips or add_terminal_strip by effect, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-apply guidance (apply=false default for reporting, ask the user before applying because numbers change) and a solid exclusion list of what is deliberately left untouched. It stops short of naming an alternative tool for the excluded cases, so it is not a full when/when-not routing statement.

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