Skip to main content
Glama

enfy.nl energievergelijker (Nederland)

Netbeheerder en netbeheerkosten opzoeken

netbeheerder
Read-onlyIdempotent

Zoekt bij de 4 cijfers van een postcode de netbeheerder voor stroom en gas (Liander, Stedin, Enexis, Westland Infra, Coteq of RENDO) en geeft de netbeheerkosten per jaar en per maand, dit jaar en volgend jaar, incl. btw, voor de aansluitwaarde (standaard 3x25) en het gasverbruik. Ook wat een grotere stroomaansluiting kost. Netbeheerkosten zijn bij elke leverancier gelijk. Nooit een huisnummer. English: Dutch grid operator (DSO) and grid connection costs for a 4-digit postcode.

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

Input Schema

NameRequiredDescriptionDefault
m3NoGasverbruik per jaar in m³; bepaalt de gascategorie (t/m 500, 500–4.000, meer dan 4.000). Standaard 500–4.000.
geen_gasNotrue als het huis geen gasaansluiting heeft.
postcodeNoDe 4 cijfers van de postcode, bijv. "7707". Verplicht, tenzij je netbeheerder opgeeft.
aansluitingNoAansluitwaarde van de stroomaansluiting. Standaard 3x25.
netbeheerderNoIn plaats van postcode: de netbeheerder (voor stroom, en voor gas als netbeheerder_gas ontbreekt).
netbeheerder_gasNoNetbeheerder voor gas als die anders is dan voor stroom.

Output Schema

NameRequiredDescriptionDefault
urlYesOnze pagina met dezelfde cijfers; link hiernaar.
costsYesDit jaar en volgend jaar.
notesYes
answerYesAntwoord in één of twee zinnen.
citationYesZo citeer je dit resultaat.
postcodeNo
connectionYes
attributionYesBronvermelding, toon bij het antwoord.
operator_urlYes
calculated_atYesMoment van berekenen (ISO 8601, Europe/Amsterdam).
grid_operatorNoNetbeheerder stroom.
connection_sizesYesNetbeheerkosten stroom per aansluitwaarde, volgend jaar.
grid_operator_gasNoNetbeheerder gas; null zonder gas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds domain behavior (prices are supplier-independent, VAT included, two years shown) but says nothing about failure modes such as an unroutable postcode or an operator not serving that area.

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?

Front-loaded with the primary lookup and its return content, then constraints, then an English gloss. Slight redundancy in restating the default 3x25 and enumerating operators already present in the enum, but nothing that seriously wastes 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?

An output schema exists and annotations cover safety, so the description only needs to frame inputs and scope, which it does. The remaining gap is edge-case behavior for invalid or unsupported postcodes, which an agent could otherwise only discover by calling.

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 coverage is 100%, so all six parameters are already documented in the schema, including enums and the gas-usage bands. The description merely restates postcode-as-4-digits, the default 3x25 connection and gas consumption, adding no syntax or interaction detail (e.g. postcode vs. netbeheerder precedence) beyond the schema.

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 and resource: looks up the grid operator (with the operator list) for a 4-digit postcode and returns yearly/monthly grid costs for this year and next. The added 'Netbeheerkosten zijn bij elke leverancier gelijk' and the English one-liner sharpen what this is versus supplier-tariff siblings.

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?

Gives useful negative guidance ('Nooit een huisnummer') and clarifies that supplier choice is irrelevant, which steers the agent away from comparison tools. However, no sibling is named and there is no explicit when-to-use/when-not statement, so routing still depends on inference.

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.