Skip to main content
Glama

enfy.nl energievergelijker (Nederland)

Zo vergelijken we: methode, dekking en actualiteit

methode_en_dekking
Read-onlyIdempotent

Hoe de vergelijking werkt en hoe volledig en actueel de gegevens zijn: volgorde alleen op kosten (geen betaalde volgorde), hoe de welkomstbonus telt, wat wel en niet in de bedragen zit, privacy; hoeveel leveranciers en producten in de vergelijking staan (en welke niet, met reden), de laatste tariefcontrole per leverancier (oudste en nieuwste), tot welke dag we dynamische stroom- en gasprijzen hebben en welke jaren energiebelasting en netbeheertarieven we kennen. Met leverancier: of die leverancier erin staat en wanneer we hem controleerden. Geen bedragen. English: how the comparison works (ranking method, independence, coverage of Dutch energy suppliers, data freshness, last tariff check).

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

Input Schema

NameRequiredDescriptionDefault
leverancierNoOptioneel: naam of slug van een leverancier (bijv. "Eneco") om te zien of die in de vergelijking staat en wanneer we hem controleerden.

Output Schema

NameRequiredDescriptionDefault
urlYesOnze pagina met dezelfde cijfers; link hiernaar.
linksYes
marketYesTot welke dag we marktprijzen hebben.
privacyYesWelke gegevens we vragen en bewaren.
rankingYesHoe de volgorde tot stand komt.
citationYesZo citeer je dit resultaat.
coverageYes
includedYesWat in de bedragen zit.
supplierNoAlleen met leverancier: die leverancier.
referenceYes
attributionYesBronvermelding, toon bij het antwoord.
not_includedYesWat niet in de vergelijking of de bedragen zit.
calculated_atYesMoment van berekenen (ISO 8601, Europe/Amsterdam).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), but the description adds real behavioral context: no paid ranking, how the welcome bonus is counted, what is and isn't included in amounts, privacy stance, oldest/newest tariff check per supplier, how far dynamic prices extend, and which tax years are known. That is substantive disclosure of what the response will and won't contain, well beyond the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is front-loaded with the core purpose, but the body is a single semicolon-chained sentence enumerating many sub-topics, and the trailing English one-liner duplicates the Dutch content for an agent that already parsed it. Information density is high and little is filler, yet the wall-of-text structure makes scanning harder than a short bulleted breakdown would.

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 read-only meta/informational tool with a single optional param and an output schema (so return values need not be spelled out), the description covers every dimension an agent would need: ranking, independence, coverage gaps with reasons, per-supplier freshness, dynamic price horizon, and known tax years. Nothing material 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 the optional leverancier param is already documented in the schema, so the baseline is 3. The description does add the concrete effect — whether that supplier is included and when it was last checked — but this largely restates the schema description rather than adding new semantics (no slug/name format nuance beyond the schema's own examples).

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 definition states precisely what the resource is: comparison methodology (ranking, independence, bonus handling, privacy) plus coverage and data freshness, with the explicit constraint 'Geen bedragen' that separates it from the price-comparison siblings. The verb is explanatory rather than a single action verb, but the scope is unmistakable and an agent can tell it apart from vergelijk_energie or leverancier_tarieven.

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: 'Geen bedragen' signals this is the meta/methodology tool rather than a price tool, and the optional leverancier param signals a per-supplier check. However, it never explicitly names an alternative ('for actual prices use X') or states when not to call it, so the routing to siblings must be inferred.

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.