Vektis MCP

Overview Schema Source Related Servers Discussions Admin

agb_search_organisaties

Search the Dutch AGB register for healthcare businesses and locations by AGB-code, name, place, postcode, KvK number, zorgsoort, or kwalificatie, and view address details.

Instructions

Search the AGB-register for ondernemingen (businesses) and vestigingen (locations).

Require at least one non-empty query, location, KvK, zorgsoort or kwalificatie criterion. Results include record_type and an address when available.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	AGB-code or name. Digits match as a substring of the code, letters match the name. May be omitted when filtering on plaats, postcode or kvknummer.
`plaats`	No	City name.
`postcode`	No	Four digits, optionally followed by two letters, e.g. '9403' or '9403AA'.
`kvknummer`	No	KvK-nummer, up to 12 digits.
`zorgsoort`	No	Two-digit zorgsoort code. Omit for all. 01 Huisartsen \| 02 Apothekers \| 03 Medisch Specialisten \| 04 Fysiotherapeuten \| 05 Logopedisten \| 06 Ziekenhuizen \| 07 Oefentherapeuten \| 08 Verloskundigen \| 11 Tandarts - Specialisten (Mondziekten en Kaakchirurgie) \| 12 Tandartsen \| 13 Tandarts - Specialisten (Dento-Maxillaire Orthopedie) \| 14 Bedrijfsartsen \| 17 Rechtspersonen \| 18 Dialyse Centra \| 19 Audiologische Centra \| 20 Radiotherapeutische Centra \| 21 Dienstenstructuren (ANW-Diensten) \| 22 Zelfstandige Behandelcentra \| 23 Instellingen voor Revalidatiedagbehandeling \| 24 Dietisten \| 25 Instellingen voor Psychiatrische Deeltijdbehandeling \| 26 Podotherapeuten \| 30 Instellingen voor Verstandelijk Gehandicapten \| 31 Bloedbanken \| 32 GGD \| 33 Kraamzorg \| 34 Trombosediensten \| 35 Instellingen voor Visueel Gehandicapten \| 36 Ambulancediensten \| 37 Gezondheidscentra \| 38 Tandheelkundige Centra \| 39 Instellingen voor Jeugdtandverzorging \| 40 Instellingen voor Auditief Gehandicapten \| 41 ZZP-ers in wijkverpleging/ PGB aanbieders / Beheerstichtingen \| 42 Verzorgingshuizen \| 43 Beheerstichtingen Verzorgingstehuizen \| 44 Optometristen \| 45 Verpleeginrichtingen voor Somatische Ziekten \| 46 Verpleeginrichtingen voor Psycho-Geriatrische Patienten \| 47 Gecombineerde Verpleeginrichtingen \| 48 Overige Instellingen \| 49 Abortusklinieken \| 50 Laboratoria(Huisartsenlab./Gemeensch.Lab/Gemeensch Apoth+Lab \| 51 Klinisch-Genetische Centra \| 52 Eurotransplant \| 53 Diverse Samenwerkingsverbanden \| 54 GGZ Instellingen (PUK/PAAZ) \| 56 Consultatiebureaus voor Alcohol en Drugs \| 58 Centrale Post Ambulancediensten - CPA \| 60 Instellingen voor Dagverpleging voor Ouderen \| 61 Beheerstichtingen Dagverblijven \| 65 Gezinsvervangende Tehuizen \| 66 Koepels en Beheerstichtingen WLZ \| 67 Netwerk organisaties \| 70 Kinderdagverblijven \| 72 RIBW \| 73 WLZ Gecombineerd \| 74 Arbodiensten \| 75 Thuiszorginstellingen \| 76 Leveranciers Hulpmiddelen \| 78 Sociaal Pedagogische Diensten \| 79 RIAGG \| 84 Overige Artsen \| 85 Taxivervoerders \| 87 Mondhygienisten \| 88 Ergotherapeuten \| 89 Schoonheidsspecialisten \| 90 Overige therapeuten en Complementair en Aanvullende zorg \| 91 Verpleegkundigen \| 93 Tandtechnici / Tandprothetici \| 94 Psychologische Zorgverleners \| 96 Pedicuren \| 98 Declaranten/Servicebureaus/Zorgverzekeraars
`include_ended`	No	Keep records that have an einddatum.
`kwalificaties`	No	Kwalificatie codes to filter on, e.g. ['0100']. 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.5/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 behavioral burden. It does disclose a validation rule (at least one filter required) and that results carry record_type and an address 'when available', which is useful. It says nothing about permissions, pagination, or the limit ceiling, leaving meaningful 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the search scope and then the precondition. The closing note on record_type/address borders on redundant given an output schema exists, but it is brief and does not bloat the definition.

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-value detail is not required, and the description supplies the one piece of structured data that is missing: the at-least-one-criterion constraint. The remaining gaps (result volume/limit behavior, include_ended semantics) are minor given the rich schema descriptions.

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 88%, so the schema already documents each of the 8 parameters in detail, including the full zorgsoort enum and postcode/KvK patterns. The description only restates the filter categories that must be satisfied, adding little parameter-level meaning beyond the baseline for high-coverage schemas.

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?

The description gives a specific verb ('Search') and resource ('AGB-register for ondernemingen and vestigingen'), and the entity scope (businesses/locations) implicitly separates it from the sibling agb_search_zorgverleners. It does not name that sibling explicitly, so the differentiation still requires a small inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence states a genuine precondition – at least one of query, location, KvK, zorgsoort or kwalificatie must be non-empty – which is real usage guidance beyond the schema. However, it never routes the agent toward agb_search_zorgverleners, agb_get_record, or agb_lookup_codes, so when-not-to-use and alternative selection are left implicit.

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

Deploy Server