Skip to main content
Glama

Electricity spot prices today and tomorrow

get_electricity_spot_prices
Read-onlyIdempotent

Day-ahead wholesale electricity prices for a Danish or Swedish bidding zone (DK1, DK2, SE3, SE4) for today or tomorrow: the day's average, the lowest and highest interval, the price now and the hourly averages, in euro per MWh and in the local currency per kWh. Before VAT, tax and grid fees. Data: Energinet, CC BY 4.0.

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>"
    },
    "name": "get_electricity_spot_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoThe zone's own calendar day. Tomorrow's prices are usually published between 13:00 and 14:00 Central European Time. Default: today.
zoneYesBidding zone: DK1 (western Denmark), DK2 (eastern Denmark), SE3 (Stockholm area), SE4 (southern Sweden)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent, closed-world), so the description earns credit for the extras it supplies: the Energinet source, the CC BY 4.0 license, and the crucial caveat that prices are before VAT, tax and grid fees. It also discloses what the response contains (average, min/max interval, price now, hourly averages) and in which two units, which matters because there is no output schema.

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?

A single dense but well-ordered sentence front-loads the resource, then zones, days, returned figures, units and the tax-basis caveat, closing with source and license. Every clause carries information an agent would otherwise have to guess.

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 two-parameter read-only tool with no output schema, the description covers what is returned, in what units, on what pricing basis, from which source, and when tomorrow's data appears. Nothing an agent needs to call and interpret it correctly is missing.

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 100% and both parameters carry enums with their own descriptions, so the schema already does the heavy lifting. The description reinforces the zone list and the today/tomorrow scope but adds no parameter-level detail (formats, defaults, edge cases) beyond the schema, so the baseline 3 applies.

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 names a specific resource and scope: day-ahead wholesale electricity prices for named bidding zones (DK1, DK2, SE3, SE4) and named days. The resource is unambiguous against siblings like get_fuel_prices or get_ecb_rates, so an agent can route correctly without opening the schema.

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 tells the agent the data exists for today or tomorrow and the schema adds the publication window for tomorrow's prices, which is the main usage constraint. It does not spell out exclusions or failure behavior when tomorrow's data is not yet published, so it stops short of explicit when-not guidance.

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