ro-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RO_ELI_ENDPOINT | No | The SOAP endpoint URL for the Romanian Portal Legislativ. | https://legislatie.just.ro/apiws/FreeWebService.svc/SOAP |
| RO_ELI_AUDIT_DIR | No | Directory for audit logs. | ~/.matematic/audit |
| RO_ELI_CACHE_DIR | No | Directory for caching API responses. | ~/.matematic/cache/ro-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 |
|---|---|
| ro_searchA | Search Romanian legislation. Provide at least one of |
| ro_get_actA | Fetch Romanian act metadata by number + year (disambiguate with tip_act). |
| ro_get_textA | Fetch the full Romanian text of an act by number + year (disambiguate with tip_act). |
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 3 tools
Each tool has a clearly distinct purpose: ro_search finds acts based on criteria, ro_get_act retrieves metadata, and ro_get_text retrieves the full text. Even though get_act and get_text share parameters, their outputs are different and descriptions are explicit.
The naming follows a consistent pattern with the 'ro_' prefix and verb-noun structure (ro_search, ro_get_act, ro_get_text). ro_search is slightly shorter than the others but still clearly aligned, making the set predictable.
Three tools is well-scoped for a legislation retrieval server. Each tool covers a distinct, essential step in the workflow: search, metadata lookup, and full text access.
The tool surface covers the complete lifecycle for a read-only legal database: discovering acts via search, retrieving structured metadata, and accessing the full text. No obvious gaps are present for the stated purpose.