Renewable Vision energy data

Saudi power balance

power_balance

Read-only

Saudi renewable capacity operational, under construction and tendered, against the 2030 National Renewable Energy Program target and against the Principal Buyer’s own register, with what changed since last month and which projects the register corrected on stage. With month, the balance as it was stored for that month rather than recomputed.

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

Input Schema

Name	Required	Description	Default
`month`	No	A stored month, YYYY-MM; omit for the current balance

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish that this is a safe, closed-world read operation. Beyond that, the description adds meaningful behavior: it reports operational, under-construction, and tendered capacity; includes month-over-month changes and register corrections; and clarifies that a stored month is returned as stored rather than recomputed.

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 definition is front-loaded with the core data scope and avoids filler, but the first sentence is dense and packs several distinct concepts together. It remains readable and appropriately sized for a focused data-retrieval tool.

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 one-parameter read-only data tool with annotations and no output schema, the description covers the resource, comparison targets, monthly storage behavior, and what kinds of changes are included. It is largely complete, though it could be stronger with explicit sibling routing guidance.

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 100%, so the schema already documents the optional YYYY-MM month and its omission behavior. The description adds semantic value by clarifying that a requested month returns the balance as stored for that month rather than a recomputed figure.

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 identifies a specific resource: Saudi renewable capacity broken down by operational, under-construction, and tendered status, compared against the NREP 2030 target and the Principal Buyer register. It does not explicitly distinguish itself from sibling balance tools such as oil_balance, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains how the optional month parameter changes the result, but gives no explicit guidance on when to use this tool versus alternatives like oil_balance or other outlook tools. The use case is implied by the domain, not stated as a routing rule.

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?