Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Override strip part quantities

set_strip_parts

Override accessory counts on a terminal strip, such as end plates, end stops, jumper bars, or markers. Set a quantity to replace the count Ohmstead works out from blocks, or use 0 to remove the part.

Instructions

Override how many of a part a strip needs (accessories: end plates, end stops, jumper bars, markers, or any extra part). Ohmstead works these out from the blocks; an override replaces that count (0 removes the part). qty null = back to the worked-out count. Block counts can't be overridden; change the terminals instead.

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

Input Schema

NameRequiredDescriptionDefault
partsYes
stripYesStrip tag, e.g. TB1
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the bar is lower. The description adds genuine behavioral context beyond them: how overrides interact with computed counts, that 0 deletes the part, and that null restores the default. It does not mention permissions or what the response looks like, and there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the action and scope before the edge-case semantics (0, null) and the exclusion. Nothing is padding.

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 three-required-parameter mutation with no output schema, the description covers the essential semantics an agent needs to call it correctly. Minor gaps remain around project_id/strip meaning and the shape of the result, but the core behavior is complete.

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 coverage is only 33%, so the description must carry weight, and it does: it explains qty as an override with 0 and null as special values, and clarifies which part categories are eligible. project_id remains unexplained, and the part-level schema for 'strip' and 'part' is only briefly described.

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 ('Override how many of a part a strip needs') and scopes it tightly: accessories like end plates, end stops, jumper bars and markers. It also rules out block counts, which cleanly separates it from sibling tools such as set_strip_blocks.

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?

Provides concrete when-to-use semantics: an override replaces the computed count, 0 removes the part, and null reverts to the Ohmstead-derived count. It also gives an exclusion ('block counts can't be overridden; change the terminals instead'), though it names the workflow rather than the exact sibling tool.

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