eu-law-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_eu_lawA | Search authoritative CELLAR metadata for EU legislation and legal acts. Returns metadata and provenance, not legal conclusions. |
| get_eu_documentA | Retrieve an exact official language/version of an EU legal act by deterministic identifier. |
| get_articleB | Retrieve one structurally exact article, including numbered paragraphs and points, from official CELLAR XHTML. |
| get_recitalsB | Retrieve selected, source-numbered recitals from an official EU legal text. |
| compare_document_versionsB | Return deterministic structural provision differences after whitespace/markup normalization; does not characterize legal effect. |
| search_eu_casesB | Search authoritative EU case law. query is an AND-of-tokens match over official case titles. provision verifies a direct article-to-instrument citation in official numbered case paragraphs and returns that evidence. interpreted_celex is instrument-level metadata only. |
| get_eu_caseC | Retrieve an exact official EU court document with source paragraph numbering preserved. |
| get_case_paragraphsB | Retrieve only requested, source-numbered paragraphs. Missing numbers return PARAGRAPH_NOT_FOUND. |
| find_cases_citingA | Find citing judgments through authoritative CELLAR work_cites_work relationships, never keyword co-occurrence. |
| search_edpb_documentsC | Search the official EDPB document catalogue through its public website. |
| get_edpb_documentC | Retrieve text from an official EDPB PDF and preserve visible numbered paragraphs where extractable. |
| search_edps_documentsA | Search official Publications Office CELLAR metadata for EDPS publications. Coverage is limited to EDPS material deposited in CELLAR. |
| list_document_versionsB | List the original act and every official consolidation, with requested-language availability reported without substitution. |
| get_document_timelineB | Return original, corrigendum, amending-act, and consolidation events as distinct official resources. |
| get_provision_at_dateA | Return an exact article from the latest safe official snapshot on or before a date; legal effect is not inferred. |
| verify_legal_quoteA | Compare a quote only with one stored evidence anchor. Returns exact_match, normalized_match, or no_match. |
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 16 tools
Every tool targets a distinct retrieval or search operation with clear domain boundaries: legislation vs. case law vs. EDPB vs. EDPS. Even similar operations like get_article and get_provision_at_date are differentiated by identifier vs. date, and version-related tools (timeline, list, compare) have non-overlapping purposes.
All 16 tools follow a consistent verb_noun snake_case pattern (get_, search_, compare_, find_, list_, verify_). The verbs are descriptive and uniform, making the tool surface predictable and easy to navigate for an agent.
With 16 tools, the server is slightly above the optimal 3–15 range but still well-scoped for its multi-domain purpose (legislation, case law, EDPB, EDPS). Each tool earns its place, covering distinct operations without unnecessary bloat.
The set provides comprehensive coverage for a read-only legal information server: full-document retrieval, granular provision access (articles, recitals, paragraphs), version history and comparison, date-based access, and citation verification. No obvious dead ends or missing core operations are apparent.