Vektis MCP

Overview Schema Source Related Servers Discussions Admin

agb_search_zorgverleners

Search the Dutch AGB register for individual healthcare providers by AGB code or name, with optional zorgsoort or qualification filters. Returns initials-only names; use record lookup for details.

Instructions

Search the AGB-register for individual zorgverleners (huisartsen, tandartsen, fysiotherapeuten, ...).

Results carry initials-only names and no address; use agb_get_record for detail sections.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	Yes	AGB-code or name. Digits match as a substring of the code, letters match the name.
`zorgsoort`	No	Two-digit zorgsoort code. Omit for all. 01 Huisartsen \| 02 Apothekers \| 03 Medisch Specialisten \| 04 Fysiotherapeuten \| 05 Logopedisten \| 07 Oefentherapeuten \| 08 Verloskundigen \| 11 Tandarts - Specialisten (Mondziekten en Kaakchirurgie) \| 12 Tandartsen \| 13 Tandarts - Specialisten (Dento - Maxillaire Orthopedie) \| 14 Bedrijfsartsen \| 24 Dietisten \| 26 Podotherapeuten \| 33 Kraamzorg \| 44 Optometristen \| 57 Physician Assistant \| 84 Overige Artsen \| 87 Mondhygienisten \| 88 Ergotherapeuten \| 89 Schoonheidsspecialisten \| 90 Overige therapeuten en Complementair en Aanvullende zorg \| 91 Verpleegkundigen \| 93 Tandtechnici / Tandprothetici \| 94 Psychologische Zorgverleners \| 96 Pedicuren
`include_ended`	No	Keep records that have an einddatum.
`kwalificaties`	No	Kwalificatie codes to filter on, e.g. ['0101']. See agb_lookup_codes.

Output Schema

TableJSON Schema

Name	Required	Description
`results`	Yes
`has_more`	Yes	More matching rows are known to exist beyond the returned limit.
`source_total`	No	Source match count before local filtering; null when unavailable.
`returned_count`	Yes	Number of returned results after local filtering and limit.
`applied_filters`	Yes
`source_truncated`	Yes	Source render cap prevents inspecting all matches; narrow the search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a genuinely useful behavior: results carry initials-only names and no address. However, it says nothing about result limits, pagination, or why ended records are excluded by default, leaving notable behavioral gaps for a search tool.

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?

Two short sentences with zero waste; the primary purpose is front-loaded and the follow-up caveat about initials/no address plus the routing hint are tightly packed.

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, so return structure needn't be explained, and the description sensibly warns about the limited identity data returned. It is nearly complete for a search tool, missing only paging/limit behavior hints.

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 80%, so the schema already documents query, zorgsoort, kwalificaties, limit and include_ended in detail. The description adds nothing about parameter usage or syntax, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (AGB-register for individual zorgverleners), with examples of the categories covered. The word 'individual' implicitly contrasts with the sibling agb_search_organisaties, though that sibling is never named, so differentiation is left partly to inference.

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 routes the agent to agb_get_record when detail sections are needed, which is actionable guidance. It lacks an exclusion against agb_search_organisaties or advice on query construction, so it stops short of full when/when-not coverage.

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

Deploy Server