Renewable Vision energy data

One report

get_report

Read-only

One report at its permanent address: the caption as prose, the definitions of its headline figures quoted from its own notes, its sources, the cover and the public preview pages. Its figures are as filed on contentUpdated; the live dashboards are separate tools and may read differently. Public fields only — the PDF and the data pack stay behind free membership.

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": {
      "id": "<id>"
    },
    "name": "get_report"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Report id from list_reports

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already establish read-only, non-destructive, closed-world behavior. The description adds meaningful context beyond them: the report's permanent address, the fact that figures reflect contentUpdated rather than live dashboards, and that only public fields are returned while PDF/data pack require membership.

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?

The description is front-loaded with the core purpose, then moves to payload and constraints in three sentences. Some phrasing is ornate ('at its permanent address', 'quoted from its own notes'), but each clause carries useful information and is not wasteful enough to score lower.

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 simple one-id read with no output schema, the description usefully sketches the returned public fields and flags gated artifacts. It omits failure behavior for invalid ids, which keeps it from a 5.

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 coverage is 100%, and the sole id parameter is already documented as 'Report id from list_reports'. The description adds no id syntax or validation detail, so the baseline of 3 is appropriate.

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?

The description identifies a single-report retrieval by permanent address and enumerates the payload (caption, definitions, sources, cover, preview pages), which clearly distinguishes it from list_reports and live dashboards. An agent can tell this is the canonical single-report lookup.

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?

It signals when figures should come from this tool ('as filed on contentUpdated') versus separate live dashboards, and warns that the PDF and data pack are gated. It does not name those dashboard alternatives or explicitly route id discovery to list_reports in the description itself, so it is not a 5.

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?