Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Check cable sizing

electrical-engineering_cable-sizing-calculate

Compare calculated design current to caller-supplied cable ampacity. Ampacity tables are not invented. Price $0.04 USDC. POST /api/v1/electrical-engineering/cable-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_cable-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

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does usefully disclose payment and failure behavior ($0.04 USDC, POST endpoint, 402 on unpaid calls with no execution), but says nothing about what the response contains, whether checks are pass/fail, units, or what happens when ampacity data is missing.

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 comparison, and no filler. The endpoint path and price lines are boilerplate but genuinely informative for a paid API.

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 high-complexity tool with 14 top-level parameters, deep nesting, and no output schema. A two-sentence functional summary plus billing notes leaves the agent unable to know which arrays are required for the comparison, what minimum viable input looks like, or what the result represents.

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, including nested loads, cables, system, rules, and equipment arrays. The description only hints at two of them (design current and ampacityA), leaving the purpose of loads, system, rules, and the many equipment arrays unexplained in both schema and prose.

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 first sentence gives a specific verb and resource: compare a calculated design current against caller-supplied cable ampacity. That is a clear, narrow operation that reads differently from siblings like voltage-drop-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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to a sibling tool for related checks. The only implicit guidance is 'Ampacity tables are not invented', which tells the caller they must supply ampacity rather than having it looked up.

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