Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add terminal strip

add_terminal_strip

Adds a planned terminal strip with auto-tagged terminals (TB1, TB2…) and the specified or project-default terminal block. Use it when you need strips beyond those created by fanout fixes.

Instructions

Add a terminal strip (auto-tagged TB1, TB2…). Usually fix_fanouts creates strips for you; use this for planned strips. Its terminals use block if given, else the project default block, else a generic block (terminal_type, clamps_per_side).

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

Input Schema

NameRequiredDescriptionDefault
blockNoTerminal block part for this strip: part id or part number, or "PE" for the project's PE block. Omit for the project default.
subsystemNo
terminalsNo
project_idYes
terminal_typeNopush
clamps_per_sideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description usefully adds the auto-naming scheme and the block-resolution fallback chain. However, with no output schema it never says what is returned (strip id/name, created terminals) or what prerequisites exist, which matters for a creation tool.

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 short sentences, front-loaded with purpose then the routing hint then the block logic; nothing is wasted. The final sentence is dense and slightly hard to parse on first read ('Its terminals use `block` if given, else...').

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?

For a 6-parameter creation tool with no output schema, the definition covers naming, block resolution, and defaults but omits the return value and the meaning of `terminals` and `subsystem`. Adequate to call correctly in the common case, incomplete for anything beyond it.

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 description coverage is only 17%, and the description compensates for part of that: it explains the `block` fallback chain (given → project default → generic) and ties terminal_type and clamps_per_side to the generic block case. It says nothing about `terminals` (count, default 4) or `subsystem`, leaving two parameters undocumented in both places.

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?

States a specific verb and resource ('Add a terminal strip') plus a concrete side effect ('auto-tagged TB1, TB2…'). It also names the sibling fix_fanouts and clarifies the division of labor, so the agent can distinguish the two without opening either 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?

Explicitly routes the agent: prefer fix_fanouts for generated strips, use this one for 'planned strips'. It gives clear context and an alternative but no explicit when-not to use it (e.g., relating to set_strip_blocks/set_strip_parts, which could obviously apply after creation).

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