Skip to main content
Glama

entsoe-mcp

Get top-bottom spread

get_tb_spread
Read-onlyIdempotent

Top-Bottom (TBx) spread — daily battery-arbitrage benchmark. TBx = sum(top X priced hours) − sum(bottom X priced hours) over the day-ahead clearing prices for zone on date. The day is the SDAC market day (23/25 hours on DST-transition days). date must be a bare YYYY-MM-DD — time-bearing strings are rejected. Returns both spread (/MW/day) and mean_spread (/MWh = spread/X) in the zone's trading currency — see the response currency/unit (EUR for euro zones; GB=GBP). Common X: 1, 2, 4. A day past the zone's day-ahead series end (GB after 2020-12-31) answers with series_ended, naming the endpoint that carries the prices on.

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": {
      "zone": "<zone>",
      "date": "<date>"
    },
    "name": "get_tb_spread"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
dateYes
zoneYes

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?

Beyond the read-only/idempotent annotations, it discloses market-day semantics (23/25 hours on DST transitions), strict date validation that rejects time-bearing strings, currency behaviour per zone (EUR vs GBP), and a non-error `series_ended` response path with a pointer to the alternative endpoint. That is substantial behavioural context an agent could not infer from annotations.

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?

The formula is front-loaded in the first two lines, then edge cases and currency semantics follow. Every sentence carries information not available in the schema or annotations — none of it is padding.

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 three-parameter derived-metric tool with an output schema and full annotation coverage, the description leaves no material gap: computation, units, validation rules, DST handling, currency, and the series-ended fallback are all addressed.

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 load and does so for all three parameters: `x` is defined as the top/bottom count with common values 1, 2, 4; `date` is constrained to bare YYYY-MM-DD; `zone` determines the trading currency. It does not describe the accepted zone identifier format, which list_zones presumably supplies.

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 description gives a precise verb-and-resource definition with the actual formula (TBx = sum of top X priced hours minus bottom X priced hours over day-ahead clearing prices for zone/date). It is clearly a derived benchmark, distinguishable from sibling get_day_ahead_prices, which returns raw prices.

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 establishes the context (daily battery-arbitrage benchmark over SDAC market days), typical X values, and what happens past a zone's series end, including that the response names the endpoint holding the prices. It stops short of explicitly stating when to prefer a sibling such as get_day_ahead_prices for raw prices.

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