Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Calculate electrical load schedules

electrical-engineering_load-schedule-calculate

Calculate kW, kVA, and current for caller-supplied loads using supplied voltage and power factor. Missing values are not invented. Price $0.04 USDC. POST /api/v1/electrical-engineering/load-schedule-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_load-schedule-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

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral facts: missing values are not invented, calls cost $0.04 USDC, the endpoint is POST, and unpaid calls return 402 without running. However it does not state that this is a non-destructive computation with no side effects, nor what the response looks like, which matters given there is no output schema.

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 with the computation front-loaded, followed by the no-invention guarantee and the payment/endpoint mechanics. No filler, though the raw endpoint path is of limited value to an agent.

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 14-parameter tool with nested schemas, zero annotation and zero schema description coverage, and no output schema, the description is too thin: it understates the scope (it never mentions cables, breakers, generators, transformers, or power-factor cases) and gives no sense of the returned structure or units.

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 with deeply nested objects, so the description must compensate and largely does not. It only gestures at 'loads', 'voltage', and 'power factor', leaving the cables, breakers, generators, transformers, powerFactorCases, rules, and the text/csv/json/file input variants 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?

The description names a specific verb and computed quantities: 'Calculate kW, kVA, and current for caller-supplied loads using supplied voltage and power factor.' That is enough to distinguish it from siblings like cable-sizing or voltage-drop, though it never names an alternative directly.

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 when-to-use versus when-not-to-use guidance and no routing to the many sibling calculators (cable sizing, breaker rating, transformer capacity). An agent must infer from the purpose sentence that this is the general load-schedule entry point rather than a specialized check.

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