Skip to main content
Glama

HALOWERK EU Power Dispatch API

renewable_share

Carbon-aware and ESG agents buy this endpoint to measure the current renewable share and generation mix in Germany.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceYes
total_mwYes
fossil_mwYes
timestampYes
breakdown_mwYes
renewable_mwYes
renewable_share_pctYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and largely fails it. The word 'current' is the one genuinely useful cue, implying a live snapshot rather than history, but nothing is said about refresh cadence, units, data source, or whether the call has side effects. The opening marketing clause adds no behavioral information.

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

Conciseness3/5

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

It is a single short sentence, but the first half ('Carbon-aware and ESG agents buy this endpoint') is promotional framing rather than operational information, so the actual purpose arrives late and the sentence does not fully earn its place.

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?

The tool is simple (no parameters, output schema present), so return-value detail is not required. The description supplies the resource, the scope ('current'), and the geography, which is most of what an agent needs; only refresh cadence and units remain unstated.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no input is needed by framing the call as a simple measurement.

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 names a specific measurement ('renewable share and generation mix') and a specific geography ('Germany'), so the agent knows exactly what data comes back. It falls short of 5 because it makes no effort to distinguish this from adjacent siblings such as carbon_now or grid_load, leaving overlap resolution to the agent.

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

Usage Guidelines3/5

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

Usage is only implied through the target audience ('Carbon-aware and ESG agents'), which loosely signals the ESG/carbon reporting context. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling tools, so the agent must infer selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources