Skip to main content
Glama

entsoe-mcp

Get a time series

get_series
Read-onlyIdempotent

Generic time-series query for ANY registered series endpoint.

One tool covers every dataset except outages (call list_endpoints() to see them all), so a new dataset needs no new tool to learn.

Argument shape adapts to the endpoint: • single-zone (day_ahead_price, actual_load, generation_per_type, …) → pass zone="DE_LU" • cross-zone (crossborder_flow, scheduled_exchanges, net_transfer_capacity_dayahead) → pass from_zone="DE_LU" AND to_zone="FR" • psr-dependent (generation_per_type, wind_solar_forecast, installed_generation_capacity) → optionally filter via psr_types=["solar","wind_onshore"]

start/end: UTC by default; start inclusive, end EXCLUSIVE (for "all of April 2026" use end=2026-05-01). Pass tz="local" or an IANA name to interpret as wall-clock in that timezone.

aggregation: 'raw' (default — native PT15M/PT60M per endpoint), 'hourly' (AVG over quarters → one row per hour, useful for the growing list of PT15M-stored endpoints like DE_LU day_ahead_price), 'daily', or 'monthly'. For day-ahead prices specifically the auction still clears hourly even where stored at PT15M, so AVG=any-quarter; SUM would 4× over-count.

Currency: price columns keep _eur_ in their names for stability. An endpoint whose rows carry a currency column (day-ahead and intraday prices, the A81/A15 capacity prices, activated_balancing_price, imbalance_prices) labels each row (PLN, HUF, RON, CZK, GBP, …) and the response unit follows it; unit is null when the window mixes currencies (mixed_currency) or, for activated_balancing_price and imbalance_prices, holds rows of unknown currency (currency_unknown_rows). Never average a price across rows with different currency.

Split periods: when a response carries split_periods, some periods hold more than one row — different published series told apart by the listed columns (activated_balancing_price: product, e.g. CZ/SK mFRR standard A01 vs specific A02; or currency). Never average across them. Keep one with filters={"product": ["A01"]} — filters takes any categorical column of the endpoint ({column: [values]}).

Process types: activated balancing prices are one endpoint per ENTSO-E processType (activated_balancing_price = A16 realised; _mfrr_scheduled = A60, _mfrr_direct = A61, _afrr_local = A68) — different prices for the same period, never to be merged. related_series names the siblings holding data for the zone.

Ended series: a window reaching past the day a series stopped upstream (a zone that left ENTSO-E, a frozen archive, a series that ended) carries series_ended — the last day, why, and successors: the endpoints that carry it on, each with a ready call and a note on how it differs. GB day-ahead after 2020-12-31 → day_ahead_price_imrp (GBP/MWh); GB generation after 2021-06-15 → generation_per_type_elexon (Elexon, the same ENTSO-E codes) and generation_mix (NESO, with its estimate of embedded wind).

Freshness: every answer carries freshness — the newest value stored for the series (newest, UTC; the whole series, not only the window), how far back its values are fetched again, at least weekly (rechecked_days; 0 = not at all), the last day of a series its publisher stopped (stopped_after) and, where the publisher's revision lag is known, the date from which values may still change (revisable_from, with revision_basis "measured" or "estimated"), with a plain note. compare_zones, get_derivation and get_tb_spread carry it too, one entry per series read.

Outage-family endpoints (different schema) stay on get_outages().

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": {
      "endpoint": "<endpoint>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNo
endYes
zoneNo
startYes
filtersNo
to_zoneNo
endpointYes
from_zoneNo
psr_typesNo
aggregationNoraw

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / filters
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered; the description nonetheless adds substantial behavioral context the annotations cannot. It discloses end-exclusive windows, UTC-by-default timezone interpretation, that 'raw' returns native PT15M/PT60M, that averaging prices across differing currencies or split periods is invalid, and how ended series and freshness metadata surface. That is exactly the extra layer the annotations do not carry.

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?

The front matter is excellent — purpose, routing, and argument shape come first and are scannable. But the back half consists of long blocks on currency labelling, split_periods, process types, ended series and freshness, much of which restates response fields that an output schema already documents. The behavioral rules embedded in those blocks (never average across currencies or split periods) earn their place; the field-by-field enumeration of freshness keys does not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter generic dispatcher over many heterogeneous endpoints, the description supplies what an agent actually needs to call it correctly: how to discover endpoints, how to pick the right zone parameters, time semantics, aggregation choices, and the traps that would silently produce wrong numbers. Return-value detail is partly redundant given the output schema, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description bears the full burden and largely meets it: it explains which of zone vs from_zone/to_zone applies per endpoint family, what psr_types filters, that tz accepts 'local' or an IANA name, how start/end inclusivity works, and that filters takes {column: [values]}. Only the `endpoint` parameter itself is described indirectly (via list_endpoints) rather than named and exemplified.

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 opening line states a specific verb and resource ('Generic time-series query for ANY registered series endpoint') and immediately scopes it against the sibling it is not ('every dataset except outages'). An agent can distinguish this from get_outages and list_endpoints without opening any schema.

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 explicit routing: call list_endpoints() to enumerate endpoints, and outages stay on get_outages(). It also prescribes argument shape per endpoint family (single-zone vs cross-zone vs psr-dependent) with concrete examples. The gap is that convenience siblings such as get_day_ahead_prices, get_generation, get_load and get_crossborder_flow are never mentioned, so the agent is left to infer when those should be preferred over this generic tool.

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