Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Calculate voltage drop

electrical-engineering_voltage-drop-calculate

Calculate voltage drop from supplied cable resistance/reactance, length, and load current. Cable tables are not invented. Price $0.04 USDC. POST /api/v1/electrical-engineering/voltage-drop-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_voltage-drop-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
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the commercial model (price $0.04 USDC), the 402-on-unpaid behavior and that unpaid calls 'do not run', plus the endpoint. It does not say what the response contains (no output schema exists) or how results are shaped, which is a notable gap for a computation tool.

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, front-loaded with the core operation before the commercial and transport details. The endpoint URL and payment boilerplate are necessary but somewhat mechanical; nothing is wasted, though nothing is expanded either.

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 objects, zero schema descriptions, no annotations, and no output schema, the description is far too thin. It does not explain the relationship between loads and cables (the cables array carries loadId), the units expected, or what the result reports, so an agent lacks enough to invoke it correctly beyond a trivial case.

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% with 14 top-level parameters and deep nested objects, so the description must compensate. It adds meaning only for the three inputs it names (resistance/reactance, length, current), leaving csv, asOf, file, json, text, rules, system, breakers, chargers, generators, transformers, and powerFactorCases entirely undocumented in both schema and prose. The agent cannot tell which of the many accepted payloads are relevant.

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?

States a specific verb and resource: 'Calculate voltage drop' with the inputs that drive it (cable resistance/reactance, length, load current). This distinguishes it from siblings like cable-sizing or power-factor-correction by resource name alone, though the description never explicitly contrasts with them.

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?

'Cable tables are not invented' is a real usage constraint — it tells the agent it must supply resistance/reactance values rather than expect a built-in cable lookup, which is the key precondition for this tool. However, there is no explicit when-to-use versus the other electrical-engineering siblings (e.g. cable-sizing) and no stated prerequisites or failure modes beyond payment.

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