Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Calculate transformer capacity

electrical-engineering_transformer-capacity-calculate

Compare transformer rated kVA to supplied or schedule load kVA and report loading percentage. Price $0.04 USDC. POST /api/v1/electrical-engineering/transformer-capacity-calculate. 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_transformer-capacity-calculate"
  }
}

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/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add genuinely useful behavior: a $0.04 USDC cost, the POST endpoint, and the explicit failure mode that unpaid calls return 402 without executing. It does not say whether the calculation is pure/non-mutating, what the response contains beyond a percentage, or what happens with partial input.

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?

Three short sentences with the purpose front-loaded, followed by cost and the failure mode. Nothing is padded, though the raw endpoint path is arguably derivable from the tool name and adds little for an agent already given the tool identifier.

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?

For a single-purpose calculation the stated output (loading percentage) is clear, but a 14-parameter, deeply nested, zero-coverage schema with no output schema demands more than one sentence about inputs. An agent cannot tell which of the many load-bearing arrays or input formats it must supply.

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 parameters, many of them nested objects. The description only touches rated kVA and load kVA and hints at a 'schedule', leaving the alternate input forms (csv, json, text, file), the asOf field, and the roles of rules, cables, breakers, chargers, generators, and system entirely unexplained. It does not compensate for the coverage gap.

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 first sentence gives a specific verb and resource: compare transformer rated kVA against supplied or schedule load kVA and report loading percentage. That is far more informative than the title alone and distinguishes it in substance from cable, generator, and voltage-drop siblings. It stops short of naming a sibling to route against, so it lands at 4 rather than 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 choose this tool versus load-schedule-calculate or generator-sizing-calculate, nor on prerequisites such as needing a transformer entry with ratedKva. The only usage-like statement is that unpaid calls return 402, which is about billing, 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