Renewable Vision energy data

Report library

list_reports

Read-only

The report library: every report this company has filed, newest edition first, with its id, title, summary, scope, sector, edition, the date its figures were compiled, page count and cover. Public fields only — each report’s PDF and data pack are free to members and are named by their member download route. Pass an id to get_report for the quoted definitions and the sources.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Default 100

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?

Annotations already cover read-only/safe semantics, and the description adds value beyond them: results are ordered newest edition first, only public fields are exposed, and the PDF/data pack are members-only and reachable via a named download route. This access-tier detail is exactly the kind of context annotations cannot convey; only pagination behavior is left unstated.

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 scope, ordering and field list are front-loaded in the first sentence, followed by access notes and the sibling routing hint. The field enumeration is long but each item is informative; no sentence is 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, the description carries the return-shape burden and does so by listing returned fields, ordering, and the members-only nature of attached artifacts. For a single-optional-parameter listing tool this is close to complete; only pagination/limit behavior is absent.

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 single optional 'limit' parameter is fully documented in the schema ('Default 100', bounds 1-200). The description adds nothing about it, so the baseline 3 applies when the schema does the work.

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?

Opens with a specific verb+resource framing ('The report library: every report this company has filed'), states ordering ('newest edition first') and enumerates the returned fields, so an agent knows exactly what it gets without opening a schema. It also distinguishes itself from get_report by naming that sibling.

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 a concrete routing rule: 'Pass an id to get_report for the quoted definitions and the sources,' which tells the agent when the follow-up call is needed. It stops short of an explicit when-not-to-use statement for the list itself, but the split with get_report is clear.

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?