Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Calculate generator sizing

electrical-engineering_generator-sizing-calculate

Size required generator kVA from supplied load and caller diversity, reserve, and derate factors. Price $0.04 USDC. POST /api/v1/electrical-engineering/generator-sizing-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_generator-sizing-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

A3.5/5.0
Behavior3/5

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

With no annotations, the description adds useful operational context: the tool is paid ($0.04 USDC), uses POST, and unpaid calls return 402 without running. It still omits authentication requirements, whether the calculation is stateless, and what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly written sentences: purpose first, then price/endpoint, then failure behavior. There is no filler and the core action is front-loaded.

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?

This is a complex tool with a deep nested schema, 14 parameters, no annotations, and no output schema. The description covers purpose and payment behavior but does not explain how to choose among csv/json/text/file inputs, what the main objects mean, or what the calculation returns, so it is not complete for the tool's complexity.

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, including nested loads, generators, cables, and multiple input modes (csv, json, text, file). The description mentions loads and diversity/reserve/derate factors at a high level but does not explain the input-mode parameters, asOf, or the many domain objects.

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 uses a specific verb and resource: 'Size required generator kVA.' It also names the sizing inputs (load, diversity, reserve, derate), which clearly separates it from siblings like transformer-capacity-calculate and load-schedule-calculate.

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 by the purpose: call this when you need generator kVA sizing. However, the description gives no explicit when-to-use guidance, no prerequisites, and no comparison against sibling sizing tools, leaving the agent to infer the context.

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