Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Check three-phase load balance

electrical-engineering_three-phase-load-balance-check

Compare phase-leg currents from supplied loads and report imbalance percentage. Optional caller rule thresholds are compared when provided. Price $0.03 USDC. POST /api/v1/electrical-engineering/three-phase-load-balance-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_three-phase-load-balance-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

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose genuinely non-obvious operational behavior: a $0.03 USDC cost, the POST endpoint, and that unpaid calls return 402 without running. What it omits is core computational behavior — the imbalance formula, how single-phase loads map onto A/B/C legs, and what happens with invalid or incomplete load data — which matters heavily for a 14-parameter engineering calculation.

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 computational purpose is front-loaded in the first sentence and the operational facts (price, endpoint, 402 behavior) follow compactly with no filler. The payment/endpoint sentences are boilerplate but carry real information an agent needs before calling.

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?

For a complex engineering calculation with 14 parameters, nested object arrays, and no output schema, the description is thin: it never describes what the returned report contains beyond an imbalance percentage, nor how the auxiliary collections (cables, breakers, generators) influence the result. The payment mechanics are covered, but the domain behavior an agent must reason about is not.

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 description coverage is 0% across 14 top-level parameters plus deeply nested loads, cables, breakers, generators, transformers, and powerFactorCases objects, so the schema offers no semantics of its own. The description only alludes to "supplied loads" and optional "caller rule thresholds," leaving the roles of system, cables, chargers, powerFactorCases, and the csv/json/text/file input alternatives entirely unexplained.

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?

"Compare phase-leg currents from supplied loads and report imbalance percentage" gives a specific verb (compare) and a specific output (imbalance percentage), so the agent knows exactly what computation is performed. It does not distinguish itself from nearby siblings such as load-schedule-calculate or voltage-drop-calculate, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool versus the sibling calculation tools, nor on prerequisites (e.g., that three-phase systems with loads assigned to legs are required). The only conditional language — "optional caller rule thresholds are compared when provided" — describes parameter behavior, not tool selection.

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