Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Check breaker ratings

electrical-engineering_breaker-rating-check

Compare calculated design current to caller-supplied breaker ratings and continuous factors. Code rules are not invented. Price $0.03 USDC. POST /api/v1/electrical-engineering/breaker-rating-check. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "electrical-engineering_breaker-rating-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
loadsNo
rulesNo
cablesNo
systemNo
breakersNo
chargersNo
generatorsNo
transformersNo
powerFactorCasesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries real behavioral weight: it discloses the payment requirement ($0.03 USDC), that unpaid calls return 402 and do not execute, and that code rules are not invented (constraining the output to supplied rules). It omits return shape and idempotency, but the commercial and execution gating context is genuinely useful.

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?

Four short sentences, front-loaded with the core comparison and followed by useful operational facts (no invented rules, price, endpoint, 402 behavior). No filler; slightly terse for the schema's depth.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 14-parameter tool with deeply nested objects (loads, breakers, cables, generators, transformers, rules) and no output schema needs substantially more guidance than four sentences. An agent cannot tell which of these arrays are required or how they interact to produce a check result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 14 parameters, so the description must compensate and largely does not. It hints at breakers.ratingA and continuousFactor, but leaves loads, system, cables, rules, generators, transformers, csv/json/file/text and asOf entirely unexplained, leaving most nested objects undocumented.

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?

States a specific verb and resource: 'Compare calculated design current to caller-supplied breaker ratings and continuous factors.' That is unambiguous and distinct from siblings like cable-sizing or voltage-drop. It stops short of naming or contrasting a sibling, which a 5 would require.

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 only implied by the wording 'compare calculated design current' – an agent must infer it is for verifying breaker selection against already-computed loads. There is no explicit when-to-use, when-not, or alternative tool routing, and no prerequisites for the calculated input.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources