sk-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SK_ELI_BASE_URL | No | Base URL for the Slov-lex static mirror. | https://static.slov-lex.sk |
| SK_ELI_AUDIT_DIR | No | Directory for audit log. | ~/.matematic/audit |
| SK_ELI_CACHE_DIR | No | Directory for caching fetched data. | ~/.matematic/cache/sk-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 |
|---|---|
| sk_get_versionsA | List the consolidated versions of a Slovak act. |
| sk_get_actA | Fetch Slovak act metadata by year and number. |
| sk_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:
|
| sk_get_textB | Fetch the full text of a Slovak act (a consolidated version). |
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: listing versions, fetching metadata, retrieving text, and declaring coverage gaps. There is no meaningful overlap or ambiguity between the four tools.
Three tools follow a consistent sk_get_* verb pattern, and all share the sk_ prefix. sk_coverage breaks the pattern by using a noun instead of a verb, making the set slightly less uniform.
Four tools is well-scoped for a focused Slovak legal act retrieval connector. Each tool serves a distinct need without redundancy or unnecessary bloat.
The tool set covers the core lifecycle of accessing Slovak acts: retrieve act metadata, list consolidated versions, fetch full text, and know exactly what the connector does not cover. The explicit coverage tool fills potential gaps rather than leaving agents stranded.