Skip to main content
Glama
Sign In

Renewable Vision energy data

by sa.com.renewablevision
OverviewDiscussionsAdmin

What is expected next

whats_due
Read-only

The publications and milestones this platform expects next: each mirrored source with the date its refresh is due and how many days late it is, and the tracked projects carrying a stated commercial operation year. Schedule facts, not forecasts.

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

Input Schema

NameRequiredDescriptionDefault
daysNoWindow ahead in days; default 14

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish a safe, read-only, closed-world read operation. The description adds useful behavioral detail by explaining exactly what will be returned: refresh due dates, days late, and projects with a stated commercial operation year.

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?

The definition is compact and front-loaded: it names the resource, enumerates the two returned categories, and closes with a sharp positioning sentence. 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?

With no output schema, the description carries the return-value burden and does explain the main fields an agent will receive. It is nearly complete for a simple one-parameter read tool, with only minor gaps around ordering or empty results.

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%, so the single `days` parameter is already documented as the forward window with a default of 14. The description implies a forward-looking window with 'expects next' but adds no syntax or usage detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: upcoming publications/milestones, mirrored-source refresh due dates, lateness, and tracked projects with commercial operation years. It also distinguishes this from forecast tools with 'Schedule facts, not forecasts,' though it does not explicitly name a sibling tool.

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 gives clear contextual guidance by framing the tool as schedule facts rather than forecasts, which helps an agent choose it for due-date and milestone questions. It stops short of naming alternatives such as outlook or scenario tools, so the when-to-use boundary is clear but not fully routed.

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 toolsInspect
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