Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Explain sizing

explain_sizing
Read-only

Returns one wire's sizing breakdown—current, design current, gauge, ampacity, derating, voltage drop, fuse/breaker, and suggested gauge—so you can verify its design by id or endpoints.

Instructions

One wire's sizing breakdown — current, design current, gauge, ampacity and its derating, voltage drop, the fuse or breaker behind it, and the suggested gauge — the same numbers the wire's details show in Ohmstead. Find the wire by id, or by its ends like update_connection takes them.

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

Input Schema

NameRequiredDescriptionDefault
toNo"TAG:TERMINAL", e.g. "K1:A1"
fromNo"TAG:TERMINAL", e.g. "PSU1:+24V"
project_idYes
connection_idNoWire id from get_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/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 covered; the description adds that results mirror 'the same numbers the wire's details show in Ohmstead,' which reassures consistency with the UI. It stays silent on failure behavior (unknown id, no matching ends, both forms supplied) and on whether zero/empty results are possible.

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?

One dense but well-ordered sentence that front-loads the return contents before the lookup instructions. Every clause carries information, though the long dash-separated enumeration makes it slightly heavy to parse.

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 four-parameter read-only lookup with no output schema, the description spells out the returned fields thoroughly, so the agent knows what it gets back. The remaining gaps are minor: the undocumented project_id and the unstated resolution rules when id and ends conflict.

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 75% and project_id is undocumented, but the description adds genuine meaning beyond the schema by framing connection_id and the from/to pair as alternative lookup modes and by pointing at update_connection for the end format. It stops short of stating that the two modes are mutually exclusive or what happens if both are provided.

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 ('explain') and resource ('sizing' for one wire) and enumerates exactly what the breakdown contains: current, design current, gauge, ampacity with derating, voltage drop, fuse/breaker, suggested gauge. That enumeration makes it clearly distinguishable from siblings like get_project or update_connection.

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?

Gives practical guidance on how to locate the target wire ('by id, or by its ends like update_connection takes them'), which is a real usage hint. However, it never says when to reach for this tool rather than get_project or the wire's detail view, and gives no exclusions or preconditions.

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