nl-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NL_ELI_BASE_URL | No | Base URL for the KOOP SRU API. | https://zoekservice.overheid.nl/sru/Search |
| NL_ELI_AUDIT_DIR | No | Directory for audit log output. | ~/.matematic/audit |
| NL_ELI_CACHE_DIR | No | Directory for on-disk cache. | ~/.matematic/cache/nl-eli |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nl_searchA | Search Dutch consolidated acts by words in the title, in force on a date. |
| nl_get_actA | Fetch metadata for the version of a Dutch act in force on a date. |
| nl_get_textA | Fetch the full consolidated XML of a Dutch act in force on a date. |
| nl_case_searchA | List Dutch court decisions (Rechtspraak Open Data) by metadata filters. The open-data search has NO free-text query. Filter by a date range and, optionally, a
court ( |
| nl_coverageA | Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns:
|
| nl_get_decisionA | Fetch a Dutch court decision by its ECLI (Rechtspraak Open Data). |
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 6 tools
Each tool targets a clearly distinct operation: searching acts, fetching act metadata, fetching act text, searching cases, fetching a specific decision, and describing coverage. There is no realistic overlap that could lead an agent to pick the wrong tool.
All tools share the nl_ prefix, which creates a recognizable namespace, but the internal pattern is not uniform: nl_get_* uses verb-first naming, while nl_case_search is object-first and nl_coverage is a bare noun. This is a minor inconsistency rather than a confusing mix.
Six tools is well-scoped for a legal information connector covering both legislation and case law. Each tool serves a necessary retrieval or orientation purpose, and none feels redundant.
The set covers search, metadata retrieval, and full-text retrieval for acts, plus metadata-based search and full-decision retrieval for case law. The dedicated coverage tool explicitly documents limitations and fallbacks, which closes the main practical gap in legal data connectors.