nrel_pvwatts

Estimate solar PV system production using NREL's PVWatts v8 model. Returns annual and monthly AC energy output (kWh), solar resource (kWh/m²/day), and capacity factor. Used by solar developers, homeowners, and ESG analysts to size and estimate solar arrays.

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 91 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nrel-pvwatts.md

What nrel_pvwatts does on Livedatalink

AI agents call nrel_pvwatts to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
lat number Latitude in decimal degrees. Use with lon as alternative to address.
lon number Longitude in decimal degrees. Use with lat as alternative to address.
tilt number Array tilt angle in degrees (default 20).
losses number Total system losses percent (default 14).
address string Street address, city/state, or place name. Either address OR lat+lon required.
azimuth number Array azimuth in degrees (default 180 = south for northern hemisphere).
array_type number 0=fixed open rack, 1=fixed roof (default), 2=1-axis tracking, 3=1-axis backtracking, 4=2-axis tracking.
module_type number 0=standard (default), 1=premium, 2=thin film.
system_capacity number Yes System size in kilowatts DC (e.g. 5 for a 5 kW residential system).

Parameters from the server's own tool schema.

Why nrel_pvwatts is rated Low

This tool queries the NREL PVWatts model to retrieve solar production estimates. It is purely informational—reading from a calculation service and returning results to the user. No side effects, state changes, or irreversible actions occur. Appropriate for Read category with low severity since misuse would merely produce incorrect solar estimates, not compromise systems or finances.

From the tool's definition Tool 'returns' energy production estimates and solar resource data without modifying any external systems or data. Verbs indicate retrieval: 'Estimate' and 'Returns' output data.

Questions about nrel_pvwatts

What does the nrel_pvwatts tool do? +

Estimate solar PV system production using NREL's PVWatts v8 model. Returns annual and monthly AC energy output (kWh), solar resource (kWh/m²/day), and capacity factor. Used by solar developers, homeowners, and ESG analysts to size and estimate solar arrays. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does nrel_pvwatts accept? +

nrel_pvwatts accepts 9 parameters: lat, lon, tilt, losses, address, azimuth, array_type, module_type, system_capacity. Required: system_capacity. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nrel_pvwatts? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for nrel_pvwatts: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Livedatalink. Nothing to install.

What risk level is nrel_pvwatts? +

nrel_pvwatts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nrel_pvwatts? +

Yes. Add a rate_limit block to the nrel_pvwatts rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block nrel_pvwatts completely? +

Set action: deny in the PolicyLayer policy for nrel_pvwatts. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides nrel_pvwatts? +

nrel_pvwatts is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Livedatalink, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.