Vektis MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VEKTIS_USER_AGENT | No | User-Agent sent to Vektis. Set this if you want to identify your deployment instead. | a generic Chrome string |
| VEKTIS_MAX_RETRIES | No | Retries after the first attempt. | 2 |
| VEKTIS_HTTP_TIMEOUT_SECONDS | No | Per-request timeout. | 20 |
| VEKTIS_TOOL_DEADLINE_SECONDS | No | Total budget per tool call, including pacing and retries. | 60 |
| VEKTIS_REQUEST_INTERVAL_SECONDS | No | Minimum interval between requests to vektis.nl. | 1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agb_search_zorgverlenersA | 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. |
| agb_search_organisatiesA | 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. |
| agb_get_recordA | Retrieve one exact AGB registration, preserving leading zeros. Return found, not_found or ambiguous. For ambiguous, return candidates to retry with record_type. A found record includes identity, status, source_url and retrieved_at. Source failures are tool errors, never not_found responses. |
| agb_lookup_codesA | Discover zorgsoort and kwalificatie filter codes and labels. Without filters, list zorgsoorten. With zorgsoort, list its kwalificaties. With query alone, search both levels. With both, search kwalificaties under that zorgsoort. Each kwalificatie includes its parent_code. Unknown parents are input errors; an unmatched query returns an empty results list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The two search tools are cleanly split by target (zorgverleners individuals vs organisaties businesses/locations), agb_get_record is a distinct exact-retrieval operation, and agb_lookup_codes handles filter metadata. No two tools overlap in purpose.
All four tools use a consistent agb_ prefix with a clear verb_noun/snake_case pattern (search_x, get_record, lookup_codes). Predictable and readable throughout.
Four tools are well-scoped for a register-lookup service: two search entry points, one exact-get, one code-discovery helper. Each earns its place with no redundancy.
The read-only AGB domain is fully covered: search for individuals and organizations, exact record retrieval handling found/not_found/ambiguous, and code discovery for filters. No obvious operational gaps for a lookup surface.