SpotWave electricity prices

Compare all markets

compare_markets

Read-onlyIdempotent

Compares the current electricity price across every covered European market, sorted cheapest first by all-in price. All figures are EUR per kWh so markets are directly comparable. The snapshot is refreshed at most hourly (see asOfUtc) and uses the current hour's average price. All-in = variable household price per kWh: spot + energy tax + per-kWh grid fee + VAT. Fixed monthly charges (grid capacity, tax credits) are excluded. Spot = wholesale day-ahead price.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_markets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds genuinely new behavioral context: at-most-hourly refresh cadence, use of the current hour's average, the exact all-in cost composition (spot + energy tax + per-kWh grid fee + VAT), and what is deliberately excluded (fixed monthly charges, tax credits). That is the kind of domain semantics the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly five short sentences, front-loaded with the purpose and sort order, then progressively unpacking currency, freshness, and cost definitions. Every sentence adds information an agent would otherwise have to guess; the glossary-style definitions of 'all-in' and 'spot' earn their space.

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?

With no input schema and no output schema, the description carries the burden of explaining the values, and it does: units (EUR/kWh), ordering (cheapest first), freshness (asOfUtc), and cost basis. It stops short of describing the shape of each returned row (e.g. market identifier field names), which is the remaining gap.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing to disambiguate. The description's mention of asOfUtc refers to a response field rather than an input, but it usefully orients the agent to the snapshot timestamp.

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 (compares) and resource (electricity price across every covered European market) plus the sort order, so an agent immediately knows this is a cross-market ranking tool rather than a single-market lookup like get_current_price or a plain enumeration like list_markets.

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 only implied: the 'every covered market' scope signals comparison, but nothing states when to pick this over get_current_price or list_markets, nor any exclusions or prerequisites. The agent must infer the routing decision from the scope phrasing.

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

All SpotWave electricity prices tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?