Skip to main content
Glama

entsoe-mcp

Get day-ahead prices

get_day_ahead_prices
Read-onlyIdempotent

Day-ahead clearing price for a bidding zone, in the zone's trading currency (EUR for euro zones; the per-row currency column and the response unit say which — GB=GBP, PL/RO/BG carry local-currency eras).

start/end default to UTC; start inclusive, end EXCLUSIVE. For 'all of April 2026' use start=2026-04-01, end=2026-05-01 (end=2026-04-30 silently drops the final UTC day — and 1–2 local-time hours of April for European zones in CET/CEST). The response's period block shows the resolved window so you can verify (a 30-day month is 720 hours).

tz: pass "local" to interpret start/end as wall-clock in the zone's timezone, or an explicit IANA name like "Europe/Berlin". The server converts to UTC at the boundary.

GB/UK: ENTSO-E's GB day-ahead price ended 2020-12-31, when GB left European market coupling. For later windows use get_series(endpoint="day_ahead_price_imrp", zone="GB", …) — the same GB day-ahead auction, GBP/MWh, published ~D-2; a window past a series' end answers with series_ended, naming the endpoint that carries it on.

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.

Input Schema

NameRequiredDescriptionDefault
tzNo
endYes
zoneYes
startYes
aggregationNoraw

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 declare readOnly/idempotent/non-destructive, and the description adds substantive behavior: start inclusive / end exclusive, the silent-truncation pitfall of end=2026-04-30, local-vs-UTC tz conversion at the boundary, and the series_ended response when a window passes a series' end. This is context an agent cannot get from structured fields.

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 the core semantic (currency) then range semantics, then alternatives. Dense and mostly earning its space, though the GB/UK paragraph is long relative to its share of calls and could be one sentence shorter.

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 values needn't be explained, yet the description helpfully clarifies the `period` block, `unit`, and per-row `currency`. Nearly complete except for the unexplained `aggregation` parameter, which matters for a tool whose default is raw rows.

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?

Schema description coverage is 0%, so the description must carry parameter meaning — and it thoroughly explains start, end, and tz (including accepted "local" / IANA forms and conversion semantics). However the `aggregation` parameter (default "raw") is never mentioned, leaving one of five parameters undocumented anywhere.

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?

States a specific verb and resource — day-ahead clearing price for a bidding zone — and immediately names the currency dimension that distinguishes it. It also explicitly separates itself from get_series (GB after 2020) and get_derivation (weighted 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-not guidance: for GB windows after 2020-12-31 use get_series(endpoint="day_ahead_price_imrp"), and for generation-weighted metrics use get_derivation(slug="capture_price"). Both alternatives are named with concrete invocation hints.

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