Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Calculate power factor correction

electrical-engineering_power-factor-correction-calculate

Calculate required kVAR (and optional capacitance) to move from a supplied power factor to a supplied target. Price $0.03 USDC. POST /api/v1/electrical-engineering/power-factor-correction-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_power-factor-correction-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.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose non-obvious behavior: a $0.03 USDC charge, the POST endpoint, and that unpaid calls fail with 402 without executing. It does not state that the operation is a pure read-only computation with no side effects, nor anything about the response, but the payment and failure semantics are meaningfully beyond what the schema reveals.

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 core purpose front-loaded and no filler; pricing and endpoint follow in a sensible order. Slightly fragmented, since the payment and routing details sit as bare fragments rather than integrated prose, but nothing is wasted.

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 tool with 14 parameters, deep nesting, no annotations, and no output schema, the description covers only the headline calculation. An agent cannot tell from it which input shape is expected, how loads and powerFactorCases combine, or what the result contains, so it is incomplete relative to 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 parameters, many of them nested objects, so the description must compensate and largely does not. The phrases 'supplied power factor' and 'supplied target' only loosely gesture at system.powerFactor and powerFactorCases.targetPowerFactor, leaving the relationships among loads, powerFactorCases, cables, breakers, and the alternate text/file/json/csv payloads 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?

The description gives a specific verb and resource: calculate required kVAR (and optional capacitance) to move from a supplied power factor to a supplied target. That is materially more informative than the name alone and clearly distinct from siblings like cable-sizing or voltage-drop. It stops short of explicitly contrasting with any alternative, but the domain leaves little ambiguity.

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 use this tool versus the other electrical-engineering calculators, and no explanation of which input path to choose among loads, powerFactorCases, cables, or the raw csv/json/text/file payloads. The only conditional stated is the payment gate (unpaid calls return 402 and do not run), which is a precondition rather than usage guidance.

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