Renewable Vision energy data

Weekly briefs published

list_briefs

Read-only

Every weekly brief published, newest first, with its ISO week, the Sunday it covers up to, its subject in both languages and its page. Use it to find the week to pass to get_brief.

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_briefs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Default 52

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, and closed-world behavior, while the description adds useful context about ordering and returned content. However, it says 'Every weekly brief' while the limit parameter defaults to 52, and the description does not reconcile that potential truncation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the returned fields and ordering, then the routing purpose. There is no redundant or filler wording.

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 read-only list tool with annotations and full schema coverage, the description supplies the returned fields and the get_brief routing an agent needs. The only notable gap is the mismatch between 'Every weekly brief' and the default limit of 52, which could mislead about completeness.

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?

There is only one parameter, limit, and schema description coverage is 100% with default 52 and max 260 documented there. The description adds no parameter-specific meaning beyond the schema, so the baseline 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?

States a specific resource and verb: every weekly brief published, newest first, with ISO week, Sunday coverage, subjects in both languages, and page. It clearly distinguishes its listing role from get_brief by saying it is used to find the week to pass to get_brief.

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?

Explicitly gives the intended use: find the week to pass to get_brief. It does not state exclusions or when to prefer another listing tool such as latest_brief, so it stops short of full when/when-not guidance.

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?