Skip to main content
Glama

enfy.nl energievergelijker (Nederland)

Prijswijzigingen van energieleveranciers

prijswijzigingen
Read-onlyIdempotent

Gecontroleerde tariefwijzigingen en nieuwe contracten van Nederlandse energieleveranciers, nieuwste ingangsdatum eerst: oud en nieuw tarief (incl. btw, excl. energiebelasting), de ingangsdatum en wat het per maand scheelt voor een gemiddeld huishouden. Optioneel voor één leverancier of alleen wijzigingen die nog ingaan (bijv. per 1 januari). Voor de vraag "wordt mijn leverancier duurder?". English: tariff changes announced by Dutch energy suppliers (price increase or decrease).

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

Input Schema

NameRequiredDescriptionDefault
aantalNoAantal wijzigingen (standaard 10).
leverancierNoNaam of slug van één leverancier, bijv. "Eneco" of "budget-thuis". Leeg: alle leveranciers.
alleen_komendNotrue: alleen wijzigingen met een ingangsdatum vandaag of later.

Output Schema

NameRequiredDescriptionDefault
urlYesOnze pagina met dezelfde cijfers; link hiernaar.
basisYes
countsYes
changesYes
filtersYes
citationYesZo citeer je dit resultaat.
feed_urlYes
attributionYesBronvermelding, toon bij het antwoord.
calculated_atYesMoment van berekenen (ISO 8601, Europe/Amsterdam).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so safety is covered. The description adds genuinely useful behavior beyond that: fixed ordering ('nieuwste ingangsdatum eerst'), tax basis of the amounts (incl. btw, excl. energiebelasting), and that a computed monthly delta for an average household is included. It does not state what happens when no changes match the filters.

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 scoping sentence comes first, followed by filters, then the target question, then a short English gloss for cross-language agents. It is dense but every clause carries information; the only mild redundancy is the Dutch/English duplication of the core purpose.

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 an output schema present and annotations covering the safety profile, the description only needs intent and scoping, which it supplies. It even previews the return fields, so an agent knows what a record contains before calling; the only omission is behavior on empty results.

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 description coverage is 100%, so the schema already carries the parameter mechanics and a 3 baseline applies. The description still adds interpretation: 'Leeg: alle leveranciers' is reinforced, and only upcoming changes is illustrated with a real-world case ('bijv. per 1 januari'), clarifying intent rather than syntax.

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 and dataset: 'Gecontroleerde tariefwijzigingen en nieuwe contracten van Nederlandse energieleveranciers', plus the record shape (old/new tariff, effective date, monthly delta). It is clear this returns announced changes rather than current prices, though it never names or contrasts a sibling such as prijshistorie or leverancier_tarieven, so differentiation is inferred rather than stated.

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 anchors usage to a concrete user question ("wordt mijn leverancier duurder?") and explains the two optional narrowing modes (one supplier, or only upcoming changes, e.g. per 1 January). It gives no explicit when-not-to-use guidance and points to no alternative tool for the adjacent questions (current tariffs, price history).

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.