Renewable Vision energy data

Solar and wind resource for an area

solar_resource

Read-only

The long-run (2001–2020) NASA POWER climatology for one 0.5° cell (about 55 km): global horizontal and direct normal irradiance in kWh/m²/day, wind speed at 50 m in m/s, air temperature in °C and aerosol optical depth at 550 nm (dust, and so panel soiling), each as an annual mean and by month. Ask by a tracked project id (answered for its locality, never its site), by a place given as "north,east" in decimal degrees, or by a cell id. Area-level only: it is not a site measurement and must not be quoted as a plant’s yield.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solar_resource"
  }
}

Input Schema

Name	Required	Description
`cell`	No	A cell id, e.g. N24.5E46.5
`point`	No	A place as "north,east" in decimal degrees; snapped to its 0.5° cell
`project`	No	A tracker project id (Saudi, GCC or captive), e.g. sudair-pv-1500-mw

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover the read-only, closed-world safety profile, and the description goes well beyond them: data provenance (NASA POWER), temporal coverage (2001–2020), spatial resolution (0.5°, ~55 km), units for every variable, and the fact that results come back as an annual mean plus monthly breakdown. It also discloses the important behavioral quirk that a project id is answered for its locality, never its site.

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?

Two sentences, front-loaded with the resource and its resolution, then the variable list, then the resolution paths and the area-level caveat — no filler. The first sentence is very dense at roughly seventy words, which costs some readability even though every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must convey what comes back, and it does: each variable with units, plus the annual-mean and by-month structure. All three optional parameters are addressed and the key limitation (area-level, not a yield figure) is stated, which is everything an agent needs to call and interpret this tool.

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 description coverage is 100%, so the baseline is 3, and the description still adds real meaning: a project id resolves to the project's locality rather than its site, and a point is snapped to its 0.5° cell. It does not repeat the cell-id or pattern details, which the schema already carries.

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?

States a specific verb and resource: it returns the long-run 2001–2020 NASA POWER climatology for one 0.5° cell, and enumerates exactly which variables (GHI, DNI, 50 m wind speed, air temperature, AOD) in stated units. An agent can tell this apart from estimate-style siblings like project_output_estimate without opening the schema.

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?

Gives concrete invocation paths (tracked project id, "north,east" point, or cell id) and a strong exclusion: area-level only, not a site measurement, must not be quoted as a plant's yield. It does not name the sibling that should be used instead for yield, so the alternative is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Renewable Vision energy data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?