Skip to main content
Glama

entsoe-mcp

Get generation by fuel

get_generation
Read-onlyIdempotent

Aggregated generation (MW) per production type.

start/end default to UTC; start inclusive, end EXCLUSIVE. For a full calendar month set end to the first day of the next month. Pass tz="local" or an IANA name to interpret start/end as wall-clock in that timezone.

GB/UK: ENTSO-E's GB generation ended 2021-06-15. For later windows in the same ENTSO-E codes use get_series(endpoint="generation_per_type_elexon", zone="GB", …) (Elexon, from 2021); for NESO's mix with its estimate of embedded wind use get_series(endpoint="generation_mix", zone="GB", …) (2009→now, its own wind codes — list_psr_types(zone="GB") first). A window past a series' end answers with series_ended, naming both.

If you're computing a generation-weighted price metric — capture price, capture rate, value factor, merchant-PPA achieved price — use get_derivation(slug="capture_price", …) instead. It runs server-side over the full window and returns monthly rows; no row cap, no pagination.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zone": "<zone>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNo
endYes
zoneYes
startYes
psr_typesNo
aggregationNoraw

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real behavior: end is EXCLUSIVE, tz defaults to UTC, and a window past a series' end returns a 'series_ended' marker naming both series. It only hints at this tool's own row cap/pagination by contrasting get_derivation's 'no row cap, no pagination', leaving the limit implicit rather than stated.

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?

Core definition and date semantics are front-loaded, and the disambiguation paragraphs are purposeful rather than filler. The GB paragraph is dense with endpoint names, but each detail maps to a real routing decision; minor tightening is possible but nothing is clearly wasteful.

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?

An output schema exists, so return shape needs no explanation, and the tricky temporal semantics and series-end edge case are covered. The gaps are the unexplained 'aggregation' parameter and the unstated result-size limit for this tool, which matter for a 6-parameter, high-volume query.

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?

With 0% schema description coverage, the description must carry all parameter meaning; it does well for start/end (inclusive/exclusive, UTC default, month-boundary convention) and tz (local or IANA wall-clock). However, 'aggregation' (default 'raw') gets no explanation at all, and 'psr_types' is only obliquely referenced via 'per production type' and list_psr_types, without stating accepted code format.

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?

The first line states a specific resource and unit: aggregated generation in MW per production type. It actively distinguishes itself from siblings by naming get_series for GB windows and get_derivation for generation-weighted price metrics, so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use-elsewhere guidance is given for two concrete cases: post-2021 GB windows should go to get_series with named endpoints, and capture price / capture rate / value factor computations should go to get_derivation. It also gives the call convention for calendar months and timezone interpretation.

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