Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Compute PV payback, NPV, IRR and LCOE

solar-design_financial-payback
Read-onlyIdempotent

Compute simple payback, NPV, IRR and LCOE from capex, incentives, year-1 energy, degradation, O&M and price escalation. Price $0.03 USDC. POST /api/v1/solar-design/financial-payback. 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": {
      "capex": "<capex>",
      "year1EnergyKwh": "<year1EnergyKwh>",
      "energyValuePerKwh": "<energyValuePerKwh>",
      "years": "<years>",
      "discountRate": "<discountRate>"
    },
    "name": "solar-design_financial-payback"
  }
}

Input Schema

NameRequiredDescriptionDefault
capexYescapex, number. Required.
yearsYesyears, integer, from 1 to 50. Required.
omPerYearNoomPerYear, number, from 0 to any. Required.
degradationNodegradation, number, from -0.5 to 1. Required.
discountRateYesdiscountRate, number, from -0.5 to 1. Required.
omEscalationNoomEscalation, number, from -0.5 to 1. Required.
year1EnergyKwhYesyear1EnergyKwh, number. Required.
energyEscalationNoenergyEscalation, number, from -0.5 to 1. Required.
energyValuePerKwhYesenergyValuePerKwh, number. Required.
upfrontIncentivesNoupfrontIncentives, number, from 0 to any. Required.

Output Schema

NameRequiredDescriptionDefault
irrNoirr. Number.
npvNonpv. Number.
lcoeNolcoe. Number.
sourcesNosources. Array.
netCapexNonetCapex. Number.
limitationsNolimitations. Array.
paybackYearsNopaybackYears. Number.
year1CashFlowNoyear1CashFlow. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds meaningful behavior beyond that: a monetary cost per call and the exact x402 failure mode where an unpaid request returns payment terms and does not execute — something an agent must know to avoid mistaking a payment challenge for a result.

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: what it computes, what it costs, and the endpoint path, with the payment caveat last. Every sentence carries distinct information and nothing is repeated from the schema.

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 and fully documented parameters, the description only needs to cover the computation scope, cost, and payment behavior, and it does all three. The remaining gap is unit/currency convention for energy value and capex, which an agent must guess before supplying correct magnitudes.

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 coverage is 100%, so the schema baseline is already 3. The description adds interpretive meaning by tying the rate parameters to their economic role — "year-1 energy," "degradation," "O&M and price escalation" — implying these are annual rates, which the schema alone does not state (it only says "degradation, number, from -0.5 to 1"). Units/currency for energyValuePerKwh remain unspecified.

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?

Names a specific verb ("Compute") and the exact outputs produced (simple payback, NPV, IRR, LCOE), plus the input drivers that scope it (capex, incentives, year-1 energy, degradation, O&M, escalation). This clearly separates it from siblings such as solar-design_tariff-savings or solar-design_energy-yield-estimate, which do not produce these financial metrics.

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 description gives a real operational precondition — a paid call costs $0.03 USDC and an unpaid call only returns x402 payment terms without running — which is useful invocation context. However, it offers no guidance on when to choose this tool over the adjacent financial sibling (tariff-savings) or which circumstances call for NPV/IRR vs payback.

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