Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Check DC/AC ratio and inverter clipping

solar-design_dc-ac-ratio-check
Read-onlyIdempotent

Compute the DC/AC ratio and optionally estimate AC energy and clipping from a caller DC power series with constant efficiency or a PVWatts inverter curve. Price $0.03 USDC. POST /api/v1/solar-design/dc-ac-ratio-check. 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": {
      "dcNameplateKw": "<dcNameplateKw>",
      "acRatingKw": "<acRatingKw>"
    },
    "name": "solar-design_dc-ac-ratio-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
acRatingKwYesacRatingKw, number. Required.
useCecCurveNouseCecCurve, boolean. Required.
dcNameplateKwYesdcNameplateKw, number. Required.
intervalHoursNointervalHours, number. Required.
ratioWarnAboveNoratioWarnAbove, number. Required.
dcPowerSeriesKwNodcPowerSeriesKw, array. Optional.
inverterEfficiencyNoinverterEfficiency, number, from any to 1. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
warningsNowarnings. Array.
dcAcRatioNodcAcRatio. Number.
acEnergyKwhNoacEnergyKwh. Number.
limitationsNolimitations. Array.
clippedEnergyKwhNoclippedEnergyKwh. Number.
clippingFractionNoclippingFraction. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: a $0.03 USDC price and the key contract that an unpaid call returns x402 payment terms and does NOT execute — exactly the kind of side effect an agent must know before calling.

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, with capability front-loaded and the payment/endpoint facts trailing. The endpoint path is low-value for an agent but the price and unpaid-call behavior earn their place; nothing is padded.

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 explained, and annotations cover safety. Combined with full schema coverage, the description supplies the remaining crucial pieces: computational modes, cost, and the non-execution behavior on unpaid calls. Only an explicit use-vs-alternative rule is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3 and the schema carries the field-level detail. The description still adds meaning by framing dcPowerSeriesKw as the caller-supplied series and by pairing 'constant efficiency' with inverterEfficiency and 'PVWatts inverter curve' with useCecCurve, clarifying the two mutually exclusive modeling modes the schema only lists as bare fields.

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?

States a specific verb and resource (compute DC/AC ratio) and adds the optional capability (estimate AC energy and clipping), plus the two supported modeling approaches — constant efficiency vs a PVWatts/CEC inverter curve. That is enough for an agent to distinguish it from siblings like solar-design_energy-yield-estimate without opening a 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 is only implied: the word 'optionally' signals that supplying a DC power series unlocks energy/clipping estimation, and the two efficiency modes hint at caller choice. There is no explicit statement of when to pick this tool over energy-yield-estimate, nor any exclusion or prerequisite 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