Skip to main content
Glama

Zorgverzekering.chat: Dutch health insurance

Compare a policy across years

vergelijk_jaren
Read-onlyIdempotent

Shows what changed in a policy between two insurance years (jaargangen), for example 2026 and 2027: premium, coverage per category, reimbursement of non-contracted care and conditions. Useful in the switching season (overstapseizoen) to explain why a policy became more expensive or lost coverage. 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": {
      "polisId": "<polisId>",
      "jaarA": "<jaarA>",
      "jaarB": "<jaarB>"
    },
    "name": "vergelijk_jaren"
  }
}

Input Schema

NameRequiredDescriptionDefault
taalNoResponse language: nl (Dutch, default) or en (English).nl
jaarAYesEarlier insurance year, e.g. 2026.
jaarBYesLater insurance year, e.g. 2027.
polisIdYesPolicy id (polisId) of a basic policy or supplementary package, e.g. '2027-vgz-natura', as returned by the search tools.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
actiesYes
bronnenYes
aannamesYes
samenvattingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the 'information, not advice' stance and the scope of compared data, which is useful framing for how results should be surfaced. It says nothing about result size, missing-year handling, or errors, so it remains a modest addition.

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?

Three short sentences, front-loaded with the core comparison and its dimensions, then context, then the advisory disclaimer. Nothing is redundant, though the disclaimer sentence is the only borderline one and still earns its place for compliance framing.

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, full parameter documentation and complete annotations, the description only needs to convey purpose and usage framing, which it does. A minor gap is that it doesn't clarify what happens if a year pair isn't available for the policy, but nothing essential for a correct call 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%, with jaarA/jaarB, polisId pattern and taal enum all documented in the schema. The description only restates the two-year comparison with an example year pair, adding no format or constraint meaning beyond the schema. Baseline 3 is appropriate.

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 names a specific verb and resource ('shows what changed in a policy between two insurance years') and enumerates the compared dimensions — premium, coverage per category, non-contracted care reimbursement, conditions. This clearly separates it from siblings like vergelijk_polissen (different policies) and bereken_jaarkosten (cost calculation) without needing the 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?

It gives concrete usage context — the switching season (overstapseizoen) and the explanatory goal of why a policy got pricier or lost coverage — plus a clear framing that it informs rather than advises. It never names an alternative tool or an explicit exclusion case, so the agent must infer when to pick vergelijk_polissen or bereken_jaarkosten instead.

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.