Skip to main content
Glama
energidata-mcp

energidata-mcp

by batutho-dot

spot_price

Retrieves hourly day-ahead electricity prices for Danish price areas DK1 and DK2, per MWh before taxes and tariffs, for a specified local-time period.

Instructions

Day-ahead (spot) electricity price in a Danish price area, per hour, per MWh, before taxes and tariffs.

start/end: Danish local time, '2026-11-17' or '2026-11-17T06:00'; end is exclusive and defaults to the next midnight. Each hour is the mean of the four 15-minute prices in it. Data from the DayAheadPrices dataset, available from 2025-10-01; tomorrow's prices appear around 13:00.

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": {
      "area": "<area>",
      "start": "<start>"
    },
    "name": "spot_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
areaYes
startYes
currencyNoDKK

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it well: it discloses the unit (per MWh), tax/tariff exclusion, hourly aggregation as the mean of four 15-minute prices, dataset provenance, historical start date, and the ~13:00 publication window. It omits error/empty-result behavior, but the substantive characteristics an agent needs are present.

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?

Dense and front-loaded — the core definition and unit arrive in the first clause, followed by parameter semantics and then data-availability caveats. The mid-sentence line break and the 'start/end:' pseudo-heading make the layout slightly ragged, but no sentence is filler.

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?

Return values need no explanation because an output schema exists, and the description covers timezone, format, aggregation, units, and data availability — enough to call correctly. The unexplained currency option (and its DKK default, which determines output units) and the unspecified DK1/DK2 distinction are the remaining holes.

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 coverage is 0%, so the description must compensate, and it does for the hardest parameters: start/end are pinned to Danish local time, given accepted formats, and end is declared exclusive with a next-midnight default. Gaps remain: 'area' never explains what DK1 and DK2 denote, and the currency parameter and its DKK default are not mentioned at all.

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 description names a specific resource with precise scope: day-ahead spot price, Danish price area, per hour, per MWh, pre-tax. That is far more than a restated name. It does not differentiate from the siblings best_hours or co2_intensity, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent infers this is the tool for raw prices. The description does add valuable operational context (data exists from 2025-10-01, tomorrow's prices land around 13:00), which tells an agent when a call will succeed. It never says when to prefer best_hours or co2_intensity instead.

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

Deploy Server

Other Tools