Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Set strip terminal blocks

set_strip_blocks

Set the terminal block part for all or a labeled range of strip terminals. Wires keep their level; the change is refused if existing wires sit on a level the new block lacks.

Instructions

Set the terminal block part of strip terminals (a range by label, or all). Wires keep their level: bare labels become level A on a multi-level block and back. Refused if wires sit on a level the new block doesn't have. block = part id or part number; omit (null) to return the terminals to the strip default.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast terminal label (default: last)
fromNoFirst terminal label (default: first)
blockNo
stripYesStrip tag, e.g. TB1
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=false, so the safety profile is partly covered. The description adds real value beyond that: wires keep their level, bare labels become level A on multi-level blocks and back, and the operation is refused when wires sit on an incompatible level. It does not describe the response or what happens to other strip properties.

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?

Three dense sentences, front-loaded with the core action and followed by side effects and the null-reset rule. Some phrasing is compressed ('and back'), but nothing is wasted.

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 mutation tool with no output schema and five parameters, the description covers the key behavioral risks: wire-level preservation, level-A conversion, and refusal conditions. Only the return value and project_id semantics are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, with from/to/strip documented in the schema. The description adds meaning for 'block' (part id or part number, null to reset to strip default), which is the undocumented parameter. project_id remains unexplained in both, so it only partially compensates for the coverage gap.

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: 'Set the terminal block part of strip terminals', with scope clarified as 'a range by label, or all'. This distinguishes it from sibling setters like set_strip_parts and set_block_positions by naming the exact object being changed, though it never explicitly contrasts with them.

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 usage conditions: pass a label range or all, and 'omit (null) to return the terminals to the strip default'. It also states a precondition for refusal (wires on a level the new block lacks). No explicit when-not-to-use or named alternative, so not a 5.

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