Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Check EV charger load capacity

electrical-engineering_ev-charger-load-capacity-check

Check EV charger design current against caller-supplied panel capacity and existing load. Continuous factors are used only when supplied. Price $0.04 USDC. POST /api/v1/electrical-engineering/ev-charger-load-capacity-check. 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_ev-charger-load-capacity-check"
  }
}

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?

With no annotations, the description carries the full burden and does supply genuine behavioral facts: pricing ($0.04 USDC), the 402 failure mode for unpaid calls, that failed payments do not execute the calculation, and that continuous factors apply only when supplied. It says nothing about what the calculation returns, how conflicts between chargers/panel capacity are resolved, or whether results include pass/fail verdicts.

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 purpose before pricing and transport details. Every sentence carries information, though the raw endpoint path adds little for an agent and the commercial lines could be condensed.

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 deep nested objects, zero schema descriptions, and no output schema, the description is far too thin. An agent cannot tell which of the many arrays are required versus optional, how ids link chargers to breakers and cables, or what the response shape is.

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, many of them nested arrays (chargers, loads, breakers, cables, rules, system, generators, transformers, powerFactorCases). The description only gestures at panel capacity, existing load, and continuous factors, and never explains the alternative input channels (csv vs. json vs. text vs. file). It leaves the bulk of the contract 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?

States a specific verb and resource: check EV charger design current against caller-supplied panel capacity and existing load. This is clearly distinct from siblings like transformer-capacity-calculate or breaker-rating-check, though the description never names an alternative to route against.

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?

The verification framing implies when the tool applies (EV charger load vs. panel headroom), and 'caller-supplied panel capacity' hints that the caller must provide baseline data. There is no explicit when-to-use/when-not guidance, no prerequisites, and no pointers to related siblings such as load-schedule-calculate.

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