Skip to main content
Glama

Zorgverzekering.chat: Dutch health insurance

Check care provider contract status

check_zorgaanbieder
Read-onlyIdempotent

Checks per basic policy whether a care provider (zorgaanbieder, by AGB code) has a contract with the insurer (gecontracteerd) for a care type (zorgsoort), and which percentage of the costs is reimbursed without a contract. Each result states its origin (herkomst: insurer publication, the insurer's provider search (zorgzoeker), or cache) and the date it was retrieved. If herkomst is null the dataset has no contract information for that policy (status onbekend); calling again does not change that. Contracts can change during the year, so suggest the user confirms with the insurer. 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": {
      "agbCode": "<agbCode>",
      "polisIds": "<polisIds>",
      "zorgsoort": "<zorgsoort>",
      "jaar": "<jaar>"
    },
    "name": "check_zorgaanbieder"
  }
}

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
agbCodeYesAGB code (8 digits) of the care provider, from zoek_zorgaanbieder.
polisIdsYesBasic policy ids (polisId) to check, e.g. from zoek_basisverzekeringen.
zorgsoortYesType of care (zorgsoort), lowercase key such as 'ziekenhuis' (hospital), 'kliniek', 'ggz' (mental healthcare), 'fysio', 'wijkverpleging', 'apotheek'.

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
Behavior5/5

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

Beyond the annotations (already declaring readOnly, idempotent, non-destructive), it discloses result provenance via herkomst (insurer publication, zorgzoeker, cache) plus retrieval dates, and warns contracts can change during the year so the user should confirm with the insurer. It also frames the output as informational, not advice, and clarifies that a null herkomst means no contract data exists rather than a transient failure.

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 core capability is front-loaded in the first sentence, with provenance and the null-herkomst caveat following logically. It is slightly long, and the closing 'information, not advice' sentence is tangential to invocation, though it does clarify the tool's role.

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?

For a read-only lookup tool with a full output schema, the description covers what is needed: inputs' provenance, what a result contains (herkomst and date), what null means, and the staleness caveat. Nothing essential for correct invocation 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%, so the schema already documents agbCode, polisIds, zorgsoort, jaar and taal. The description only restates the meaning of a few of these (AGB code, per basic policy, zorgsoort) without adding format, defaults, or edge-case guidance beyond what the schema provides.

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: it checks per basic policy whether an AGB-coded care provider is contracted for a zorgsoort, and reports the reimbursement percentage without a contract. This is clearly distinct from the sibling zoek_zorgaanbieder, which the description implicitly references as the source of the AGB code.

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?

The description gives clear usage context: it points to zoek_zorgaanbieder and zoek_basisverzekeringen as sources for the inputs, and warns that if herkomst is null the dataset has no contract information (status onbekend) and re-calling will not change that. It lacks an explicit 'use this instead of X' exclusion relative to sibling tools, but the workflow and the anti-retry rule are clearly stated.

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.