eurlex-mcp-server

eurlex_search

Read-onlyIdempotent

Search EU legal acts by title substring, with optional filters for date range, language, and document type.

Instructions

Searches EU legal acts by title substring (contiguous phrase, case-insensitive — not tokenized full-text search). For topic-based discovery use eurlex_by_eurovoc instead. Broad single-word terms can be slow; narrow with resource_type or date_from/date_to. Supports all 24 official EU languages (pass the Cellar 3-letter code, e.g. DEU, ENG, FRA, POL, SPA); match the query term to the chosen language. Results are newest-first within the fetched sample, not necessarily the globally newest match for very broad queries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results
`query`	Yes	Title substring to search for, e.g. "artificial intelligence high risk". Matched as a contiguous phrase, case-insensitive.
`date_to`	No	Filter up to this date, format YYYY-MM-DD
`language`	No	Language of the title and full text, as a Cellar 3-letter code (any of the 24 official EU languages, e.g. DEU, ENG, FRA, POL, SPA)	ENG
`date_from`	No	Filter from this date onward, format YYYY-MM-DD
`resource_type`	No	Document type filter: REG=regulation, DIR=directive, DEC=decision, JUDG=judgment, REG_IMPL=implementing regulation, REG_DEL=delegated regulation, RECO=recommendation, ORDER=court order, OPIN_AG=Advocate General opinion	any

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes	Number of results in `results`
`results`	Yes	Matching acts, newest-first within the sample

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.4.2Sep 7, 2026
Removedv2.3.0Jul 22, 2026
First observedv2.2.0Jul 10, 2026

TDQS

A5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses behavior beyond the annotations: it explains that matching is a contiguous, case-insensitive phrase (not tokenized full-text), and that results are newest-first within the fetched sample, not necessarily globally newest for broad queries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is succinct yet information-dense, consisting of multiple short clauses that cover the main purpose, usage caveats, language support, and result ordering without unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and the detailed parameter descriptions, the tool description is complete for an agent to decide when and how to use it, including performance hints and result ordering nuances.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already provides descriptions for all parameters, the description adds extra semantic clarity, such as instructing users to match the query term to the chosen language and explaining that language applies to both title and full text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches EU legal acts by title substring, and explicitly differentiates it from eurlex_by_eurovoc for topic-based discovery. The verb and resource are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on when to use this tool versus the alternative (topic-based discovery via eurlex_by_eurovoc) and advises narrowing broad queries with resource_type or date filters to avoid slow performance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server