Renewable Vision energy data

Estimated output of solar projects (PVGIS model)

project_output_estimate

Read-only

Estimated annual generation (GWh) and capacity factor of solar projects in the Saudi tracker, the GCC tracker and the Saudi captive segment, modelled with PVGIS (EU JRC) at the town or region centroid — never the plant — for a fixed array at the optimal tilt and for a single-axis tracker, with totals by tracker and stage. Pass project (a tracker id such as sudair-pv-1500-mw) for one project, or filter by tracker, stage and country. The list of projects is a layer of the Energy Atlas and is free with membership: it needs a member’s API key; one project by project answers anyone. Modelled, not measured: quote it as an estimate.

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": "project_output_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`stage`	No
`country`	No
`project`	No
`tracker`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), so the description's added value is the auth/membership distinction and the important caveat that values are modelled at a town or region centroid rather than plant coordinates, with 'quote it as an estimate' guidance. It does not disclose list behavior such as the `limit` default or how many projects come back by default.

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?

Front-loaded with what is returned and how it is modelled, then access rules, then the estimate caveat — a sensible order. The opening sentence is long and stacks several parentheticals ('(EU JRC)', '(GWh)'), and 'Modelled, not measured' partially repeats 'modelled with PVGIS', but no sentence is pure filler.

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?

With no output schema and five parameters, the description still conveys return units (GWh, capacity factor), the two array configurations, and that totals break down by tracker and stage. Missing pieces are the default behavior when no filters are supplied and the role of `limit`, which an agent would have to guess.

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 coverage is 0%, so the description must carry the load: it explains `project` with a concrete id format example (sudair-pv-1500-mw), maps `tracker` to the three named trackers, and covers `stage` and `country` as filters — four of five parameters. The `limit` parameter is never mentioned, leaving its default and cap meaning undocumented.

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 (estimate) and resource (annual generation in GWh and capacity factor of solar projects), plus the exact scope: Saudi tracker, GCC tracker, Saudi captive segment. The methodology (PVGIS, town/region centroid, fixed optimal-tilt vs single-axis tracker) unambiguously separates it from siblings like solar_resource or search_projects without needing their schemas.

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 clear routing instructions: pass `project` for one project, or filter by tracker, stage and country. It also states who may call what (list needs a member API key; single-project answers anyone), which is real usage context. It stops short of naming an alternative tool or an explicit 'do not use this when...' exclusion.

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?