entsoe-mcp

Get a time series

get_series

Read-onlyIdempotent

Generic time-series query for ANY registered series endpoint.

One tool covers every (non-outage) endpoint in the registry, so adding a new dataset (call list_endpoints() to see the current 14) gets an MCP surface automatically — 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_mix (NESO).

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

Input Schema

Name	Required	Default
`tz`	No
`end`	Yes
`zone`	No
`start`	Yes
`filters`	No
`to_zone`	No
`endpoint`	Yes
`from_zone`	No
`psr_types`	No
`aggregation`	No	raw

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / filters

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: end is exclusive, tz controls wall-clock interpretation, aggregation meanings are explained, currency/unit behavior is documented, split_periods and series_ended responses are described, and process-type distinctions are spelled out. It also correctly stays consistent with readOnlyHint, idempotentHint, and destructiveHint=false.

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?

Although long, the description is front-loaded with the core purpose and then organized by argument shape, time semantics, aggregation, and edge cases. For a 10-parameter generic tool spanning 14 endpoints, the length is justified and every section supplies actionable invocation guidance.

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?

An output schema exists, so return-value structure need not be restated, yet the description still explains important response nuances such as currency units, mixed_currency, split_periods, related_series, and series_ended successors. Combined with full parameter guidance, it is complete enough for an agent to invoke the tool correctly.

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% across 10 parameters, so the description carries the full burden and does so effectively. It explains endpoint selection, start/end semantics, tz, aggregation, zone vs from_zone/to_zone shapes, psr_types, and filters with concrete examples and constraints.

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 first sentence states a specific verb and resource — a generic time-series query over any registered non-outage endpoint — and explicitly excludes the outage family. It clearly distinguishes itself from get_outages and list_endpoints, but it does not address when to use it versus specialized siblings such as get_day_ahead_prices, get_generation, get_load, or get_crossborder_flow.

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?

The description gives clear usage context: call list_endpoints to see available endpoints, choose argument shapes based on endpoint type, and use get_outages for outage-family endpoints. However, for a generic tool surrounded by specialized siblings, it does not explicitly say when to prefer those siblings over get_series, leaving the main alternative-routing question partially unanswered.

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

All entsoe-mcp 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?