Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Compute NEC 690.8 PV circuit current

solar-design_nec-690-current
Read-onlyIdempotent

Compute PV circuit maximum current and minimum conductor ampacity using NEC 690.8 125% factors for the selected code edition. Price $0.02 USDC. POST /api/v1/solar-design/nec-690-current. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "moduleIsc": "<moduleIsc>"
    },
    "name": "solar-design_nec-690-current"
  }
}

Input Schema

NameRequiredDescriptionDefault
editionNoedition, string, one of 2017, 2020, 2023. Required.2023
moduleIscYesmoduleIsc, number. Required.
parallelStringsNoparallelStrings, integer, from any to 9007199254740991. Required.
continuousFactorNocontinuousFactor, number. Required.

Output Schema

NameRequiredDescriptionDefault
editionNoedition. String.
sourcesNosources. Array.
limitationsNolimitations. Array.
minOcpdRatingNominOcpdRating. Number.
maxCircuitCurrentNomaxCircuitCurrent. Number.
perStringMaxCurrentNoperStringMaxCurrent. Number.
minConductorAmpacityNominConductorAmpacity. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds genuinely non-obvious behavior: a $0.02 USDC charge, the POST endpoint, and the critical failure mode that an unpaid call returns x402 payment terms without executing. That payment-gating detail is the main thing an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with no filler: what it computes, what it costs, and how payment affects execution. The core purpose is front-loaded ahead of the commercial and transport details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and the description covers purpose, cost, and payment failure behavior. The only minor gaps are the interaction between continuousFactor and the stated 125% default and any unit conventions, which the schema also leaves thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every parameter, and the baseline of 3 applies. The description contributes a little by tying the 125% multiplier to the computation and by explaining that a code 'edition' is selected, but it says nothing about how continuousFactor interacts with the default 1.25 factor or about units.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a precise verb and two concrete outputs ('PV circuit maximum current and minimum conductor ampacity') tied to a specific code clause (NEC 690.8) and code edition. That is specific enough to separate it from adjacent siblings such as string sizing or DC/AC ratio checks without opening the schema.

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 context is implied by the NEC 690.8 reference and the edition selection, which tells the agent this is a code-compliance calculation. However, there is no explicit when-to-use versus when-not, and no named alternative for related sizing questions (e.g., string sizing), so routing is left to inference.

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