Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Fix fan-outs

fix_fanouts

Route fan-outs through terminal strips—one per electrical net, jumpered as needed—to match the app's Fix all, using default or PE blocks as required.

Instructions

Route every fan-out through terminal strips (one strip per electrical net, jumpered as needed), same as the app's "Fix all". New strips use the project default block (update_project default_block); protective-earth fan-outs get the PE block (default_pe_block, else a generic PE block). terminal_type only applies to generic blocks.

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

Input Schema

NameRequiredDescriptionDefault
project_idYes
terminal_typeNopush

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive mutation, and the description adds meaningful behavior: one strip per net, jumpering as needed, default block selection, PE block fallback, and the scope of terminal_type. It does not discuss reversibility, permissions, or what happens to existing strips beyond the new-strip rules.

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?

The description is three dense sentences with the core routing behavior front-loaded. Parenthetical details are useful, and there is little wasted wording.

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 two-parameter mutation tool with no output schema, the description covers the essential routing and block-selection behavior. It leaves some operational details unstated, such as return values or handling of existing fan-outs, but is largely complete for correct invocation.

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 description coverage is 0%, so the description must carry parameter meaning. It explains that terminal_type only applies to generic blocks and clarifies block selection via project defaults and PE fallback; project_id is not described but is self-evident as the target project.

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 verb and resource: route every fan-out through terminal strips, with one strip per electrical net. It is clear what the tool does, though it does not explicitly differentiate itself from related siblings such as optimize_strips.

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?

Usage is implied by the reference to the app's "Fix all" and by the operation itself, but there is no explicit when-to-use or when-not-to-use guidance. No alternative tool is named for cases where the agent might not want to fix all fan-outs.

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