Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Validate project

validate_project
Read-only

Validates a wiring project for fan-outs, signal clashes, missing signals, invalid terminals/parts, supply overloads, clamp range violations, and wire/fuse sizing issues, returning suggested values.

Instructions

Check a project for fan-outs (too many wires on a terminal), signal clashes (different signal types on one net), incomplete rows, missing signals, and terminals/parts that don't exist. Also reports supply overloads, wires outside their terminal block's clamp wire range, and sizing findings (wire too small, below the minimum size, fuse too big, missing fuse rating, voltage drop over the limit) with suggested values from the project's sizing standard.

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

Input Schema

NameRequiredDescriptionDefault
project_idYes

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear; the description adds real substance by disclosing that sizing findings come with suggested values drawn from the project's sizing standard, and that checks span supply overloads and clamp wire ranges. It stops short of saying what happens on an invalid or partially-built project_id, which keeps it from a 5.

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 check categories are front-loaded into the first sentence and the second sentence groups the electrical/sizing findings, so an agent can skim the first clause and get the gist. The second sentence is a long comma-chained list with nested parentheticals, which is dense but each item adds distinct information.

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?

There is no output schema, so the description must carry the burden of describing results. It names the finding categories well but says nothing about the response shape, severity levels, counts, or whether findings are grouped per terminal/net; combined with the absent parameter documentation, an agent knows what will be checked but not what it will receive.

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 0% and the single parameter (project_id) is never mentioned in the description. Because the parameter name is self-explanatory and there is only one, the practical impact is small, but the description does nothing to confirm the expected identifier form or whether the project must already exist.

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 opens with a specific verb+resource ("Check a project") and then enumerates the exact defect classes it detects: fan-outs, signal clashes, incomplete rows, missing signals, nonexistent terminals/parts, supply overloads, clamp-range violations, and sizing findings. This is clearly a diagnostic/validation operation and is distinguishable from mutation siblings like update_project or remediation siblings like fix_fanouts.

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 rather than stated: an agent can infer this is the read-only audit step before or after edits, but there is no explicit when-to-use guidance, no preconditions (must the project be fully wired?), and no pointer to fix_fanouts for remediating the fan-outs this tool reports. The enumerated finding types imply coverage but do not route the agent among alternatives.

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