Related Servers

Each tool has a clearly delineated purpose, and the descriptions actively disambiguate near-neighbors: eurlex_search (title substring) vs eurlex_by_eurovoc (topic-based), eurlex_search (legislation) vs eurlex_case_law, and eurlex_fetch vs eurlex_consolidated vs eurlex_summary vs eurlex_metadata each target a distinct facet (full text, merged in-force text, plain-language overview, structured metadata). eurlex_structure and eurlex_sparql are also unambiguous as a map and an expert escape hatch respectively.

All names share a consistent eurlex_ snake_case prefix with a single-word suffix, which is highly predictable. There is minor mixing between verb-style suffixes (search, fetch) and noun/adjective-style suffixes (metadata, citations, structure, consolidated), but the pattern remains readable and each suffix accurately signals the operation.

Eleven tools is well within the sweet spot and each earns its place by covering a genuinely distinct EUR-Lex capability (search, retrieval, metadata, citations, transposition, case law, summaries, structure, raw SPARQL). There is no obvious redundancy or filler in the set.

The surface covers the full lifecycle of EU legal research: discovery (search, eurovoc, case law), retrieval (fetch, consolidated, structure), enrichment (metadata, citations, summary, transposition), and an expert escape hatch (sparql). Cross-references between tools (e.g. structure offsets feeding fetch) close potential dead ends, and no major operation for the domain appears missing.