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 the stored data. 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.

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

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is settled. The description then adds genuinely useful non-schema behavior: no row cap/pagination, `series_ended` propagation when upstream inputs stop (GB day-ahead ending 2020-12-31), and currency-key pitfalls where fixed `*_eur_per_mwh` names do not track the authoritative `currency` column. These are real behavioral disclosures that go well beyond the annotations.

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?

Purpose and the client-side alternative are front-loaded, which is good, but the body is sprawling: the currency paragraph runs long with multiple caveats, and column-by-column return listings duplicate what the output schema already provides. Information density is high, yet the reader must wade through prose to reach parameter behavior.

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

Completeness3/5

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

For a nine-parameter, multi-mode tool the description is unusually thorough on the hard parts (currency mixing, series termination, per-slug return shapes). Two parameters (`from_zone`, `to_zone`) are entirely unexplained, and `tz`'s default of 'local' is never stated, so an agent still cannot confidently populate every input.

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?

Schema description coverage is 0%, and the description supplies meaning for slug (six enumerated values), zone (multi-zone 'all'/list/CSV, tb_spread only), aggregation (monthly default vs annual, tb_spread only) and psr_types (labels or raw B-codes, defaults to all with generation data). However `from_zone` and `to_zone` are never mentioned anywhere, and `tz` appears only inside an example rather than as a documented parameter with its 'local' default.

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?

Opens with a specific verb and resource: it computes generation-weighted market metrics (capture price, capture rate, TBx spreads) server-side. It names the concrete slugs available and explicitly distinguishes itself from sibling tools (list_derivations for slugs, get_tb_spread for single-day top/bottom hour timestamps).

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?

Gives an explicit when-to-use rule: '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.' It also routes the agent away for the timestamp-level case ('For a single day's top/bottom hour TIMESTAMPS use get_tb_spread') and notes where slugs come from.

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