Skip to main content
Glama

enfy.nl energievergelijker (Nederland)

Dynamische stroomprijs per uur

stroomprijs_vandaag
Read-onlyIdempotent

Dynamische stroomprijs (day-ahead, Nederland) per uur voor vandaag, morgen (na ±13:00) of een datum: kaal (beursprijs excl. btw en energiebelasting) en all-in (incl. inkoopvergoeding, energiebelasting en btw), met de prijs nu, het goedkoopste blok van 3 uur, het duurste uur en negatieve uren. Optioneel met de inkoopvergoeding van één dynamische leverancier. English: dynamic (hourly, day-ahead) electricity price in the Netherlands today or tomorrow, cheapest hours.

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": "stroomprijs_vandaag"
  }
}

Input Schema

NameRequiredDescriptionDefault
datumNo"vandaag" (standaard), "morgen", "gisteren" of JJJJ-MM-DD.
leverancierNoSlug van een dynamische leverancier (bijv. "frank-energie") voor de all-in-prijs met diens inkoopvergoeding.

Output Schema

NameRequiredDescriptionDefault
nowNoHet uur of kwartier van nu (alleen voor vandaag).
urlYesOnze pagina met dezelfde cijfers; link hiernaar.
dateYes
unitYes
hoursYes
sourceYes
summaryYes
citationYesZo citeer je dit resultaat.
supplierNo
timezoneYes
validatedYes
fetched_atNo
resolutionYesPT60M (uur) of PT15M (kwartier) op de markt.
attributionYesBronvermelding, toon bij het antwoord.
all_in_basisYes
calculated_atYesMoment van berekenen (ISO 8601, Europe/Amsterdam).

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?

The annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds real behavior beyond that: the ±13:00 availability cutoff for tomorrow, the fact that both a bare exchange price (excl. VAT and energy tax) and an all-in price are returned, and that negative hours can occur. It does not state currency or unit, which is the one behavioral/format gap left.

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?

The core purpose and date semantics are front-loaded in the first clause, and the long sentence is dense rather than padded. The trailing English restatement is useful for cross-language matching but is partly redundant with the Dutch text, keeping this just under top marks.

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 a full output schema, the description need not explain return values, and the annotations cover safety. It also covers the pricing composition and the tomorrow-availability rule. The notable omission is unit/currency (EUR per kWh) and timezone, which an agent quoting prices would want.

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 100% and both parameters are documented in-schema, so the baseline is 3. The description adds value by explaining what the 'leverancier' parameter changes – the all-in price gains that supplier's purchase fee (inkoopvergoeding) – and by clarifying the bare-versus-all-in split that the date parameter selects between.

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 – hourly day-ahead electricity prices for the Netherlands, for today, tomorrow, or a given date – and enumerates the derived outputs (current price, cheapest 3-hour block, most expensive hour, negative hours). That is enough for an agent to tell it apart from gasprijs_vandaag or prijshistorie without opening a 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 gives concrete invocation contexts – 'vandaag' as default, 'morgen', or an explicit date – and adds the crucial timing rule that tomorrow's prices appear only after about 13:00. It does not name an alternative tool or state when not to use this one, so it stops short of full routing 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.