hu-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HU_ELI_BASE_URL | No | Base URL for the Hungarian legislation database (NJT) | https://njt.jog.gov.hu |
| HU_ELI_AUDIT_DIR | No | Directory for audit log of calls | ~/.matematic/audit |
| HU_ELI_CACHE_DIR | No | Directory for caching resolved legislation data | ~/.matematic/cache/hu-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 |
|---|---|
| hu_get_actA | Fetch metadata for a Hungarian Act (torveny) by its ELI (year + serial). |
| hu_get_legislationA | Fetch metadata for any Hungarian legislation by its ELI (type + year + issuer + serial). Use this for anything other than Acts (torveny) - government decrees, ministerial decrees,
etc. Use |
| hu_get_textA | Fetch the full document HTML content of a Hungarian piece of legislation. For Acts (torveny), pass |
| hu_list_doc_typesA | List valid NJT document-type codes (e.g. TV=Act, R=decree) from /eli/tipuskodok. Returns:
|
| hu_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:
|
| hu_list_issuersA | List valid NJT issuer codes (case-sensitive, e.g. Korm=Government) from /eli/kibocsatokodok. Returns:
|
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
The tools mostly partition cleanly: hu_get_act and hu_get_legislation both fetch metadata, and for Acts there is potential overlap, but the descriptions clearly route Acts to hu_get_act and everything else to hu_get_legislation. The remaining tools are distinct, covering text retrieval, code lookups, and coverage declarations.
All tools share the hu_ prefix and mostly follow a get/list verb pattern, which makes the set predictable. hu_coverage is the one naming outlier since it uses a bare noun rather than a verb_noun form, but the inconsistency is minor.
Six tools is well-scoped for a focused read-only legal connector: metadata retrieval for Acts, metadata retrieval for other legislation, full-text retrieval, two code-list helpers, and a coverage declaration. Each tool has a clear role with no obvious redundancy.
The set covers the core identifier-driven workflows: resolve document types and issuers, fetch metadata by ELI, and retrieve full text. The main gap is the absence of a search or browse capability, but the server explicitly frames itself around known ELI identifiers and documents its coverage gaps through hu_coverage.