Skip to main content
Glama

Wattpath solar energy-balance estimate

size_solar
Read-only

Use when you need solar energy arithmetic from supplied assumptions; see Data APIs. Off-grid PV energy-balance estimate based on Wattpath by Nomad Energy Club. Supply daily loads, peak sun hours, PV losses, and optional battery assumptions. No location/weather lookup, electrical design, surge or installation certification. $0.02 per calculation; no stored inputs. Price: 0.02 USDC. Minimal input example: {"loads":[{"watts":100,"hours_per_day":5,"quantity":1,"kind":"dc"}],"peak_sun_hours":4,"pv_loss_fraction":0.2,"panel_watts":200,"battery":{"voltage":12,"usable_fraction":0.8,"autonomy_days":2}}. Illustrative output excerpt: {"daily_energy_wh":{"battery_side":400},"pv":{"minimum_nameplate_watts":125,"rounded_up_watts":125},"assumptions":{"energy_balance_only":true,"weather_or_location_lookup":false}}. Illustrative output excerpt, not a live result, signature, approval or guarantee. Freshness/data/availability checks still apply. How to pay (MCP): First use the existing shared allowance of 3 eligible calls per IP per UTC day, without payment metadata. This is shared with eligible HTTP trials, not a new allowance. Use an x402-capable MCP client. A generic MCP connector without payment support cannot complete a paid continuation. On payment required, STOP. Inspect the exact accepts amount, asset, network and payTo; obtain explicit wallet/budget approval before continuing. Only after approval, let the configured x402 MCP client attach its signed payload in _meta["x402/payment"] and retry the same tools/call arguments. Never send a separate USDC transfer or paste keys into tool arguments. Never silently fall back from free access to payment. If a signed attempt has an unknown outcome, inspect that authorization/transaction; do not create another automatically.

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": {
      "loads": "<loads>",
      "peak_sun_hours": "<peak_sun_hours>",
      "pv_loss_fraction": "<pv_loss_fraction>"
    },
    "name": "size_solar"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadsYesRequired. Array of 1–50 load objects describing watts, hours_per_day, quantity and ac/dc kind. Example: [{"watts":60,"hours_per_day":4,"quantity":1,"kind":"dc"}].
batteryNoOptional. Battery assumptions object. Example: {"voltage":12,"usable_fraction":0.8,"autonomy_days":2}. Omit to skip battery sizing.
panel_wattsNoOptional. Individual panel rated power number in watts, 1–2000. Example: 400. Supply to estimate panel count.
peak_sun_hoursYesRequired. Equivalent daily full-sun hours number, 0.01–24 for a usable estimate. Example: 4.5. Supply your own site assumption; no weather lookup.
pv_loss_fractionYesRequired. PV loss fraction number, 0–0.95, not a percentage. Example: 0.2 means 20% loss.
inverter_efficiencyNoOptional. Inverter efficiency fraction number, 0.1–1. Example: 0.9 means 90%. Required when any load has kind ac; otherwise optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedInput schema / properties / battery / description
      Added value: +"Optional. Battery assumptions object. Example: {\"voltage\":12,\"usable_fraction\":0.8,\"autonomy_days\":2}. Omit to skip battery sizing."
    • addedInput schema / properties / battery / properties / autonomy_days / description
      Added value: +"Required. Required energy autonomy number in days, greater than 0 and at most 30. Example: 2."
    • addedInput schema / properties / battery / properties / existing_capacity_ah / description
      Added value: +"Optional. Existing battery capacity number in ampere-hours, 0–1000000. Example: 100. Omit when not comparing existing capacity."
    • addedInput schema / properties / battery / properties / usable_fraction / description
      Added value: +"Required. Usable battery capacity fraction number, 0.05–1. Example: 0.8 means 80%."
    • addedInput schema / properties / battery / properties / voltage / description
      Added value: +"Required. Battery voltage number in volts, 1–1000. Example: 12."
    • addedInput schema / properties / inverter_efficiency / description
      Added value: +"Optional. Inverter efficiency fraction number, 0.1–1. Example: 0.9 means 90%. Required when any load has kind ac; otherwise optional."
    • addedInput schema / properties / loads / description
      Added value: +"Required. Array of 1–50 load objects describing watts, hours_per_day, quantity and ac/dc kind. Example: [{\"watts\":60,\"hours_per_day\":4,\"quantity\":1,\"kind\":\"dc\"}]."
    • addedInput schema / properties / loads / items / properties / hours_per_day / description
      Added value: +"Required. Daily operating time number in hours, 0–24. Example: 4."
    • addedInput schema / properties / loads / items / properties / kind / description
      Added value: +"Required. Load power type enum string: ac or dc. Example: dc. AC loads require inverter_efficiency."
    • addedInput schema / properties / loads / items / properties / quantity / description
      Added value: +"Optional. Device count integer, 1–100. Example: 2. Defaults to 1."
    • addedInput schema / properties / loads / items / properties / watts / description
      Added value: +"Required. Per-device power number in watts, 0–100000. Example: 60."
    • addedInput schema / properties / panel_watts / description
      Added value: +"Optional. Individual panel rated power number in watts, 1–2000. Example: 400. Supply to estimate panel count."
    • addedInput schema / properties / peak_sun_hours / description
      Added value: +"Required. Equivalent daily full-sun hours number, 0.01–24 for a usable estimate. Example: 4.5. Supply your own site assumption; no weather lookup."
    • addedInput schema / properties / pv_loss_fraction / description
      Added value: +"Required. PV loss fraction number, 0–0.95, not a percentage. Example: 0.2 means 20% loss."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's added burden is low but it still contributes real value: per-calculation pricing ($0.02 / 0.02 USDC), 'no stored inputs', freshness/availability caveats, and a detailed free-trial-then-x402 payment procedure. It also discloses that a plain MCP connector cannot complete a paid continuation, which is genuine behavioral context. The payment narrative is long but not contradictory.

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

Conciseness2/5

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

Roughly half the text is a multi-sentence payment/safety protocol with repeated warnings ('STOP', 'Never send a separate USDC transfer', 'Never silently fall back...'), which crowds out tool-specific content. The illustrative input and output examples largely duplicate the schema's example arguments. Structure is front-loaded on purpose but the overall length-to-information ratio is poor.

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?

For a read-only calculation tool with a full schema, the description covers inputs, cost model, payment mechanics, and an illustrative output shape (daily energy, minimum nameplate watts, assumptions flags). It explicitly says the excerpt is not a live result or guarantee, which prevents over-reading. Only minor gaps remain, such as error behavior for invalid combinations like ac loads without inverter_efficiency.

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 every parameter is already documented with types, ranges, and examples. The description only restates the parameter groups at a high level ('supply daily loads, peak sun hours, PV losses, and optional battery assumptions') and its example duplicates the schema's example arguments verbatim. It adds nothing about semantics (e.g. what battery sizing does when omitted) beyond what the schema already carries, so baseline 3 applies.

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 names a specific resource and operation: 'Off-grid PV energy-balance estimate based on Wattpath', and states the inputs it consumes (daily loads, peak sun hours, PV losses, battery assumptions). It also carves out the negative scope ('No location/weather lookup, electrical design, surge or installation certification'). The wording is clear but the purpose sentence is buried under payment boilerplate and example payloads, so it is not maximally front-loaded.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when you need solar energy arithmetic from supplied assumptions' gives a clear trigger, and the exclusion list tells the agent when not to use it (no weather/location lookup, no design or certification work). No sibling tool overlaps, so the absence of named alternatives is acceptable. It stops short of stating prerequisite knowledge (e.g. where peak sun hours come from), which is only implied.

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.