Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Allow multiple wires on a terminal

allow_multiple_wires

Enable multiple wires to connect to one device terminal in an Ohmstead project, including two-level terminals, to model fan-out connections; set allow=false to revert to single-wire behavior.

Instructions

Let one device terminal take several wires in this project (e.g. a two-level terminal), silencing its fan-out. allow=false reverts.

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

Input Schema

NameRequiredDescriptionDefault
allowNo
terminalYes"TAG:TERMINAL"
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, non-destructive, non-open-world mutation. Beyond that, the description adds real behavioral context: the effect is to suppress fan-out warnings, and the setting is reversible via allow=false. It does not cover permissions or what happens to existing wires when toggled, but the added value over the annotations is clear.

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?

Two tight sentences, front-loaded with the core action and followed by the undo behavior. 'In this project' is mildly redundant given the project_id parameter, but the text is otherwise free of waste.

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, so the description carries the burden for a three-parameter mutation tool. It covers the effect and reversibility well, which are the critical unknowns for a toggle, but omits what a caller should expect on failure (e.g., an unrecognized terminal tag) and does not explain the project scoping parameter.

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 only 33%, with only 'terminal' documented (as "TAG:TERMINAL"). The description compensates by explaining both directions of the 'allow' flag, including its revert behavior, but leaves 'project_id' and the default value unaddressed. This is adequate but not full compensation for the low coverage.

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?

The description states a specific action on a specific resource: permitting one device terminal to accept multiple wires, with a parenthetical example (two-level terminal) that makes the concept concrete. It also names the side effect ('silencing its fan-out'), which distinguishes it from a plain connection-adding tool, though it does not explicitly name which sibling handles the alternative behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The example of a two-level terminal implies when this tool is appropriate, and 'allow=false reverts' implies the undo path. However, there is no explicit guidance on when to prefer this over fix_fanouts or whether it should be used before or after adding wires, leaving the agent to infer sequencing.

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