Skip to main content
Glama

entsoe-mcp

Get a derived metric

get_derivation
Read-onlyIdempotent

Compute capture price, capture rate (a.k.a. value factor / quality factor / Marktwertfaktor), TBx battery-arbitrage spreads, and other generation-weighted market metrics server-side from landed Parquet. Use this instead of fetching hourly prices + hourly generation yourself and weighting them client-side — server-side aggregation has no row cap and no pagination.

slug: a key from list_derivations() — today: "capture_price", "negative_price_hours", "residual_load", "res_share", "emissions", "tb_spread".

tb_spread returns monthly (default) or annual (aggregation='annual') Top-Bottom spreads TB1/TB2/TB4/TB6 in /MW per period — the sum of daily (top-x minus bottom-x hourly prices) over SDAC market days. The only slug accepting aggregation, and the only one accepting multi-zone zone ('all', a list, or CSV). Example — annual TB2 across every European market in ONE call: get_derivation("tb_spread", "2025-01-01", "2026-01-01", zone="all", aggregation="annual") For a single day's top/bottom hour TIMESTAMPS use get_tb_spread.

capture_price returns monthly rows per (zone, psr_type, currency) with columns: currency, capture_price_eur_per_mwh, baseload_price_eur_per_mwh, quality_factor (the capture rate = capture/baseload), total_gen_mwh, n_hours. Months are bucketed by local time using the zone's IANA timezone.

ENDED INPUTS: when an input series stopped upstream before the window's end, the answer carries series_ended (per zone for a multi-zone tb_spread): which inputs, why, what carries each on, and any metric that carries this one on. GB: ENTSO-E's day-ahead price ended 2020-12-31, so GB capture_price, negative_price_hours and tb_spread stop there; capture_price_mid covers GB 2016-09 → now against the Market Index Price (a traded index, not the auction — read its note).

CURRENCY (capture_price and tb_spread alike): the *_eur_per_mwh / tb*_eur_per_mw key names are FIXED for API stability and do NOT track the actual unit — read the row's currency column, which is authoritative (EUR for euro zones, GBP for GB, PLN/RON/BGN for the PL/RO/BG local-currency eras). The response echoes it top-level as currency; a window spanning two currencies instead sets unit to null with mixed_currency: true and a currencies list. A month (or period) spanning a redenomination splits into one row PER CURRENCY, each computed only from that currency's hours — so never average or sum a price column across rows with different currency values. Summing total_gen_mwh across them IS correct: the split rows partition the month's hours rather than duplicating them. quality_factor is a ratio and stays comparable across currencies.

emissions returns monthly rows per (zone, psr_type) with columns: generation_mwh, n_hours, emission_factor_kg_per_mwh, emissions_t_co2. Production-based; IPCC AR5 lifecycle factors. Zero-emission rows (nuclear, wind, solar, hydro, geothermal, marine) appear with emissions_t_co2 = 0 — useful for stacked charts.

Filter via psr_types=["solar","wind_onshore","wind_offshore"] (or raw B-codes like "B16") to get only the technologies you care about. Defaults to all psr_types that have generation data.

Example — Spain solar capture price, last 12 months: get_derivation("capture_price", "2025-05-01", "2026-05-01", zone="ES", psr_types=["B16"], tz="Europe/Madrid") Example — Germany 2024 emissions by fuel: get_derivation("emissions", "2024-01-01", "2025-01-01", zone="DE_LU", tz="Europe/Berlin") Returns 12 monthly rows in one call; no pagination.

Input Schema

NameRequiredDescriptionDefault
tzNolocal
endYes
slugYes
zoneNo
startYes
to_zoneNo
from_zoneNo
psr_typesNo
aggregationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, closed-world profile, and the description adds substantial behavior the annotations cannot: server-side aggregation limits, the series_ended signal with the GB/ENTSO-E cutoff and the capture_price_mid carry-on, per-slug row shapes, and the mixed_currency split-row rule with the warning not to average price columns across currencies.

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?

Front-loaded with purpose and the client-side-vs-server-side routing, then broken into labeled sections per slug and per caveat, which makes it scannable despite its length. The currency section is genuinely long and could be tightened, but each block carries non-redundant information.

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 9-parameter, multi-mode tool with an output schema, the description covers output columns, units, filtering, failure/ended-input semantics, and worked examples in three regimes. The remaining gap is the unexplained `to_zone`/`from_zone` pair, which leaves the caller guessing about a documented capability.

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?

With 0% schema description coverage, the description carries the burden well: it enumerates all slug values, explains that only tb_spread accepts `aggregation` (monthly vs annual) and multi-zone `zone` ('all', list, or CSV), and demonstrates `psr_types` with both names and raw B-codes plus `tz`. However, `to_zone` and `from_zone` are never mentioned at all, and `start`/`end` format is only inferable from examples.

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?

Names the specific resources (capture price, capture rate, TBx spreads, emissions) and the specific operation (server-side generation-weighted aggregation from landed Parquet). It enumerates the exact slugs available and distinguishes each slug's output, so an agent knows precisely what it gets without opening a schema.

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?

Explicitly says when to use it over the alternative workflow ('instead of fetching hourly prices + hourly generation yourself and weighting them client-side') and names the concrete reason (no row cap, no pagination). It also routes to siblings: list_derivations() for slugs and get_tb_spread for a single day's top/bottom hour timestamps.

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