Skip to main content
Glama

Zorgverzekering.chat: Dutch health insurance

List health insurers

list_verzekeraars
Read-onlyIdempotent

Lists all Dutch health insurers (verzekeraars) for an insurance year with their insurer group (concern), the policy types they offer (natura, restitutie, combinatie, budget), the number of basic policies and supplementary packages, and customer ratings with their source. Use it to resolve an insurer name to a verzekeraarId for the other tools. Provides information, not advice: the user makes the decision and signs up with the insurer themselves.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jaar": "<jaar>"
    },
    "name": "list_verzekeraars"
  }
}

Input Schema

NameRequiredDescriptionDefault
jaarYesInsurance year (verzekeringsjaar), e.g. 2027. During the switching season (November-December) users usually mean the coming year.
taalNoResponse language: nl (Dutch, default) or en (English).nl

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
actiesYes
bronnenYes
aannamesYes
samenvattingYes

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?

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: the 'provides information, not advice' disclaimer and the note that the user signs up with the insurer themselves, which shapes how the agent should present results. It does not discuss result volume or whether the list is exhaustive per year, which is the only remaining gap.

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?

Three sentences, no filler: the first defines the payload, the second states the routing use, the third sets the advisory boundary. The most actionable information (what you get, why you'd call it) is front-loaded before the disclaimer.

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 two-parameter read-only list tool with a full output schema and complete annotations, this description covers everything an agent needs: what is returned, the year scoping, and the intended downstream use of verzekeraarId. No explanation of return values is required because an output schema exists.

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% and the `jaar` parameter already documents the switching-season interpretation, so the schema carries the parameter burden. The description only implies year-scoping ('for an insurance year') and adds nothing about `taal` or output language selection. Baseline 3 is appropriate when the schema is this complete.

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?

Opens with a specific verb and resource ('Lists all Dutch health insurers') and then enumerates exactly what each record carries: insurer group (concern), policy types (natura, restitutie, combinatie, budget), counts of basic policies and supplementary packages, and ratings with source. This is far more specific than the sibling tools zoek_basisverzekeringen or vergelijk_polissen, so an agent can distinguish them without reading schemas.

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?

Explicitly states the primary use case: 'resolve an insurer name to a verzekeraarId for the other tools', which is exactly the routing information an agent needs to pick this tool before the insurer-specific siblings. It does not, however, name when NOT to use it or contrast it directly with zoek_basisverzekeringen/vergelijk_polissen, so it stops short of full alternative routing.

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.