fi-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FI_ELI_BASE_URL | No | Base URL for the Finlex open data API | https://opendata.finlex.fi/finlex/avoindata/v1 |
| FI_ELI_AUDIT_DIR | No | Audit directory for logging tool calls | ~/.matematic/audit |
| FI_ELI_CACHE_DIR | No | Cache directory for storing API responses | ~/.matematic/cache/fi-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 |
|---|---|
| fi_list_actsA | List Finnish statutes published in a given year. |
| fi_get_actA | Fetch statute metadata by year and number. |
| fi_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:
|
| fi_get_textB | Fetch the full Akoma Ntoso text of a statute by year and number. |
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 statutes by year, fetching metadata, fetching full text, and declaring coverage gaps. There is no overlap or ambiguity between them.
Three tools follow a consistent verb_noun pattern (fi_list_acts, fi_get_act, fi_get_text), but fi_coverage is a noun-only name that breaks the pattern. The inconsistency is minor and doesn't cause confusion.
With 4 tools, the server is small but well-scoped for a focused legal data connector. The count is slightly below the typical range but each tool serves a necessary function in retrieval and transparent coverage reporting.
The tool surface covers core read operations (list, get metadata, get text) plus explicit coverage handling, which is a thoughtful safeguard. A keyword search or version history would be a natural addition but its absence is not a critical gap for the apparent purpose.