Zorgverzekering.chat: Dutch health insurance

Statutory health insurance parameters

get_wettelijke_parameters

Read-onlyIdempotent

Returns the statutory Dutch health insurance parameters (wettelijke parameters) for an insurance year: the mandatory deductible (verplicht eigen risico), the voluntary deductible options (vrijwillig eigen risico), care exempt from the deductible, the healthcare allowance (zorgtoeslag) maximums and income and asset limits, statutory co-payments (eigen bijdragen), the premium publication date and the switching deadline (overstapdeadline). status 'voorlopig' means provisional until parliament has voted. Use this tool instead of your own knowledge for any of these amounts. 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": "get_wettelijke_parameters"
  }
}

Input Schema

Name	Required	Description	Default
`jaar`	Yes	Insurance year (verzekeringsjaar), e.g. 2027. During the switching season (November-December) users usually mean the coming year.
`taal`	No	Response language: nl (Dutch, default) or en (English).	nl

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`acties`	Yes
`bronnen`	Yes
`aannames`	Yes
`samenvatting`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world lookup. The description adds useful behavioral context beyond those annotations: it explains the meaning of provisional status and the scope boundary that this provides information rather than advice. It does not describe error handling or freshness guarantees, but the remaining gap is minor given the strong annotation coverage.

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 description is front-loaded with the core purpose and then lists the returned parameter categories in a dense but useful way. Every sentence contributes relevant scope or usage guidance. It is somewhat long, but the length is justified by the number of distinct statutory parameters covered.

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?

Given that there is an output schema and rich annotations, the description need not explain return formatting. It still provides a complete picture of what is returned, the meaning of provisional status, and the information-not-advice boundary. Nothing an agent needs in order to call this lookup correctly appears to be 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 schema already explains that 'jaar' is the insurance year and that users often mean the coming year during switching season, as well as the 'taal' enum. The description reinforces that results are for an insurance year but adds little parameter-specific meaning beyond what the schema already provides. A baseline 3 is appropriate when the schema does the heavy lifting.

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 uses a specific verb and resource: it returns statutory Dutch health insurance parameters for an insurance year. It enumerates the exact contents, including deductible amounts, care exempt from deductible, zorgtoeslag limits, co-payments, premium publication date, and switching deadline, so the agent can confidently distinguish this from calculation and comparison siblings.

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 explicitly says to use this tool instead of the model's own knowledge for these amounts, which is a strong usage instruction. It also explains that status 'voorlopig' means provisional until parliament has voted. It does not name alternative sibling tools or state when not to use it, so it falls short of full when/when-not/alternatives guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zorgverzekering.chat: Dutch health insurance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?