MCP server wrapping NLR PVWatts v8 for the Watts for Water project.
Two well-defined tools with strong parameter schemas and detailed descriptions. pvwatts_run has comprehensive input validation (lat/lon bounds, system capacity limits, enum array_type). solar_potential_for_acres provides domain-specific convenience wrapper with clear defaults. Both descriptions exceed 150 chars and explain WHEN to use each tool. However, output schemas are not explicitly documented in the source, only inferred from tool descriptions. No error handling guidance, no recovery patterns, and no tool annotations (readOnlyHint/destructiveHint). Parameter descriptions are strong but could benefit from explicit format/constraint callouts.
Faithful wrapper around NLR PVWatts v8. Use to override defaults — compare fixed-tilt vs. tracker, model a roof system, change tilt for site-specific topography. Returns annual + monthly AC/DC kWh, GHI/POA irradiance, capacity factor, and the nearest NSRDB station info.
Convenience wrapper. Takes a parcel centroid + acreage, applies Watts-for-Water project defaults (Utah utility-scale, fixed-tilt 25°, $35/MWh wholesale), and returns annual MWh, capacity factor, indicative revenue, and explicit caveats. Set tracker=true to model 1-axis backtracking (typical ~15–20% yield boost).
Output schemas not documented. Tool descriptions mention return fields (annual/monthly AC/DC kWh, capacity factor, GHI/POA irradiance, NSRDB station info) but no formal JSON schema is visible in source. LLMs cannot plan downstream operations without knowing response structure.
No error handling guidance. Tools lack recovery patterns, no indication of what errors are retryable, what user-fixable conditions exist, or what to do if NLR API is unavailable. Agents cannot self-correct on failure.
No tool annotations. Neither tool declares readOnlyHint (both are read-only), idempotentHint, or destructiveHint. Agents cannot reason about retry safety or side effects.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Parameter constraint descriptions could be more explicit. E.g., 'Latitude in decimal degrees' is clear, but 'Tilt from horizontal in degrees' lacks guidance on typical values (e.g., 'common range 0 - 45°, default 25°'). Helps LLMs avoid edge cases.
solar_potential_for_acres uses 'acres_per_mw_dc' parameter name which is domain-specific jargon. Consider 'system_density_acres_per_mw' or add explicit guidance: 'Typical values: 8 acres/MW (fixed-tilt), 5 acres/MW (tracker)' to help LLMs choose sensible overrides.