Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Estimate AC energy with PVWatts v5

solar-design_energy-yield-estimate
Read-onlyIdempotent

Estimate AC energy from caller POA irradiance and temperatures using the PVWatts v5 DC and inverter models with a transparent loss stack. Price $0.04 USDC. POST /api/v1/solar-design/energy-yield-estimate. 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": {
      "dcNameplateW": "<dcNameplateW>",
      "gammaPdc": "<gammaPdc>",
      "acRatingW": "<acRatingW>"
    },
    "name": "solar-design_energy-yield-estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthlyNomonthly, array. Optional.
recordsNorecords, array. Optional.
gammaPdcYesgammaPdc, number. Required.
acRatingWYesacRatingW, number. Required.
dcNameplateWYesdcNameplateW, number. Required.
intervalHoursNointervalHours, number. Required.
lossesPercentNolossesPercent, number, from 0 to 100. Required.
temperatureModelNotemperatureModel, object. Optional.
inverterNominalEfficiencyNoinverterNominalEfficiency, number, from any to 1. Required.

Output Schema

NameRequiredDescriptionDefault
recordsNorecords. Array.
sourcesNosources. Array.
lossStackNolossStack. Object.
totalAcKwhNototalAcKwh. Number.
limitationsNolimitations. Array.
accuracyNoteNoaccuracyNote. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world. The description adds genuinely new behavior: a $0.04 USDC price, the concrete POST endpoint, and the important fact that an unpaid call returns x402 payment terms and does not execute. It does not cover edge cases such as what happens when neither monthly nor records is supplied.

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?

Three short sentences, front-loaded with what the tool does, then cost, then the payment gate. Minimal waste; the endpoint string is arguably redundant with the description's function but is defensible for an API-style tool.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the payment behavior is well covered. However, for a 9-parameter nested tool where neither 'monthly' nor 'records' is required, the description leaves unclear which input mode to use and what intervalHours means, which is a real gap.

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 nominally 100%, so the baseline is 3, but many schema descriptions are low quality (e.g., avgAmbientTemp tagged 'gammaPdc'). The description adds that POA is caller-provided and that temperatures feed the model, but gives no meaning for intervalHours, gammaPdc, or the monthly-vs-records input modes.

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 ('Estimate AC energy') plus the underlying method (PVWatts v5 DC and inverter models with a transparent loss stack). It implicitly distinguishes itself from siblings like poa-irradiance-transpose and system-loss-stack by consuming caller-supplied POA and folding losses into an energy result, though it does not name any sibling outright.

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 phrase 'from caller POA irradiance and temperatures' implies this runs after a POA transpose step, giving a soft prerequisite. However, there is no explicit when-to-use/when-not guidance and no naming of alternatives for related tasks such as loss auditing or shading.

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