Skip to main content
Glama

BRAINIAC Electrical Engineering & Installation Intelligence

Audit electrical design documents

electrical-engineering_design-document-audit

Audit completeness of supplied electrical design inputs and aggregate load, balance, drop, cable, breaker, transformer, PF, generator, and EV checks. Does not invent code compliance. Price $0.08 USDC. POST /api/v1/electrical-engineering/design-document-audit. 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_design-document-audit"
  }
}

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 burden. It discloses payment required (price, 402 response, unpaid calls do not run), the POST endpoint, and a scope limitation ('does not invent code compliance'). However, it does not describe the response format, authentication details, or how partial or missing inputs are handled.

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?

The purpose is front-loaded in the first sentence, followed by a key behavioral caveat and operational details. The text is dense but efficient, with no redundant filler.

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 complex tool with 14 parameters, nested objects, no annotations, and no output schema, the description is incomplete. It does not explain the structure of the audit result or how the tool behaves with different input combinations, leaving the agent without enough detail to invoke it confidently.

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 nested parameters. The description names the domains of the checks but does not explain how to supply data (csv, json, text, file), what asOf or rules mean, or how the many array inputs are interpreted. It adds little meaning beyond the bare schema property names.

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 states a specific verb (audit) and resource (electrical design inputs), and lists the checks it aggregates (load, balance, drop, cable, breaker, transformer, PF, generator, EV). This distinguishes it from the sibling single-check calculators by implying an aggregate audit, though it does not explicitly say it is the aggregator alternative.

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?

Usage is implied: use this tool to audit a full set of supplied design inputs and run many checks at once. There is no explicit guidance about when to prefer this over individual sibling tools, nor any when-not-to-use conditions or prerequisites.

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