dk-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| dk_get_actA | Fetch Danish act / order metadata by ELI coordinate or accession. |
| dk_get_textA | Fetch the full LexDania XML of a Danish document (verbatim official text). |
| dk_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:
|
| dk_recent_changesA | List Danish documents changed on a given date (harvest API). |
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
Each tool has a clearly distinct purpose: metadata retrieval, full-text retrieval, coverage declaration, and change listing. No two tools overlap in what they return, making misselection unlikely.
All tools share the dk_ prefix, and most follow a verb_noun pattern (dk_get_act, dk_get_text). dk_coverage and dk_recent_changes deviate slightly by using nouns rather than verbs, but the pattern remains readable and predictable.
With four tools, the set is compact but sufficient for its narrow scope. It could benefit from a search tool, but the count is reasonable and each tool earns its place.
The core needs are covered: fetch metadata, fetch full text, list recent changes, and explicitly declare coverage gaps. Minor gaps exist—such as no search-by-keyword or version-history tool—but the dk_coverage tool mitigates uncertainty and provides fallbacks.