Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Estimate bill savings under a TOU tariff

solar-design_tariff-savings
Read-onlyIdempotent

Compute bill savings from caller interval generation and load under a time-of-use tariff with export credit, net metering or no export value. Price $0.03 USDC. POST /api/v1/solar-design/tariff-savings. 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": {
      "loadKwh": "<loadKwh>",
      "generationKwh": "<generationKwh>",
      "importPrice": "<importPrice>"
    },
    "name": "solar-design_tariff-savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadKwhYesloadKwh, array. Required.
exportModeNoexportMode, string, one of export_rate, net_metering_kwh, none. Required.export_rate
exportPriceNoexportPrice, number, from 0 to any. Required.
importPriceYesimportPrice, array. Required.
demandChargeNodemandCharge, value. Optional.
fixedChargesNofixedCharges, number, from 0 to any. Required.
generationKwhYesgenerationKwh, array. Required.
intervalHoursNointervalHours, number. Required.
billingPeriodsNobillingPeriods, array. Optional.

Output Schema

NameRequiredDescriptionDefault
savingsNosavings. Number.
sourcesNosources. Array.
exportKwhNoexportKwh. Number.
importKwhNoimportKwh. Number.
billWithPvNobillWithPv. Number.
limitationsNolimitations. Array.
billWithoutPvNobillWithoutPv. Number.
selfConsumedKwhNoselfConsumedKwh. Number.
selfConsumptionRateNoselfConsumptionRate. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower, and the description still adds real context: the $0.03 USDC price, the POST /api/v1/solar-design/tariff-savings endpoint, and the fact that an unpaid call returns payment terms instead of computing. What it does not disclose is the shape of the x402 payment terms or whether a paid retry is required, but the key behavioral surprise (a call that silently does no work) is documented.

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 compact sentences with the core purpose front-loaded and the payment/endpoint facts trailing. Every sentence carries information, though the endpoint string is more mechanical than semantic and the export-mode list could be tighter.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, tariff variants, endpoint, price, and the unpaid-call behavior. For a 9-parameter computation tool it is nearly complete, with the remaining gap being array alignment and billing-period semantics rather than anything about invocation safety.

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% and there are 9 parameters, so the schema already documents each field and the baseline is 3. The description adds the meaning of 'caller interval generation and load', implying generationKwh and loadKwh are interval-aligned series, plus the three export modes, but it does not explain interval alignment across arrays, intervalHours, billingPeriods, or the demandCharge window.

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 opens with a specific verb-and-resource pair ('Compute bill savings ... under a time-of-use tariff') and names the three export-value variants, so the agent knows exactly what is being calculated. It does not explicitly separate itself from the sibling financial-payback tool, which is the one closest in scope, so it stops short of a 5.

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 by 'from caller interval generation and load under a TOU tariff', and the description does state the operational precondition that an unpaid call returns x402 payment terms and does not run. It gives no explicit when-to-use versus solar-design_financial-payback or any other sibling, and no conditions under which this tool is the wrong choice.

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