Skip to main content
Glama
Honeyfield-Org

eurlex-mcp-server

by Honeyfield-Org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

eurlex_transposition

Read-onlyIdempotent

Retrieve national implementing measures (NIMs) for an EU directive by CELEX ID, with optional country filter. Returns official titles, dates, and EUR-Lex links for each member state's transposition.

Instructions

Lists the national implementing measures (NIMs) EU member states enacted to transpose a given EU directive into national law — the answer to "how did member state X implement directive Y" for transposition and compliance tracking. Input celex_id is the directive's sector-3 CELEX (e.g. "32022L2555" for NIS2, "31995L0046" for the Data Protection Directive); optionally filter by country (2-letter member-state code, e.g. "DE"). Each result gives the member state, the national measure's title (in that state's own official language — not translated), its date, the sector-7 NIM CELEX reference, and a EUR-Lex URL. total_found reports the full count; results is capped at limit. For the directive itself use eurlex_fetch/eurlex_metadata; regulations and decisions have no NIMs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of measures to return (1–100). The response also reports total_found (the full count).
countryNoOptional filter: EU 2-letter member-state code (ISO 3166-1 alpha-2, except Greece which is "EL" in EU usage), e.g. "DE", "AT", "FR". Omit to return measures from all member states.
celex_idYesSector-3 CELEX of the EU directive whose national transposition measures you want, e.g. "32022L2555" (NIS2) or "31995L0046" (Data Protection Directive). Member states transpose directives (CELEX type letter L); regulations and decisions generally have no national implementing measures.
languageNoSets the locale of each result's eurlex_url (as a Cellar 3-letter code, any of the 24 official EU languages). NOTE: a national implementing measure's title is stored only in the member state's own official language and is returned as-is — this field does NOT translate titles.ENG

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
celex_idYesThe directive CELEX that was queried
returnedYesNumber of measures in `results` (<= limit)
total_foundYesFull number of matching measures; when > returned, `results` was truncated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.4.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / language / default
      Previous value: -"DEU"New value: +"ENG"
  3. First observedv2.2.0

TDQS

A5/5.0
Behavior5/5

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

The description adds meaningful behavior beyond the annotations: it discloses that titles are returned as-is in the member state's own language, that total_found reports the full count while results are capped, and that omitting country returns all member states. These details complement the readOnlyHint and idempotentHint annotations.

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 comprehensive yet tightly structured, with no redundant sentences. Each sentence conveys a distinct fact (purpose, input, filter, output, language caveat, exclusions). It is long but every part is informative.

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 tool's complexity (4 parameters, enums, output schema), the description provides all necessary context: what the response contains (total_found, results), how filters behave, examples for celex_id, and clear boundaries versus sibling tools. Nothing an agent needs is missing.

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?

Schema coverage is 100% and the description enriches each parameter: celex_id includes pattern and examples, country explains the EU-specific 'EL' exception, language clarifies it does not translate titles, and limit is described in the schema. The description adds real semantic value beyond the raw schema.

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 lists national implementing measures for a given EU directive, phrased as the answer to a concrete question. It distinguishes from siblings by noting that regulations/decisions have no NIMs and directing the directive itself to eurlex_fetch/eurlex_metadata.

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?

Explicitly guides when to use this tool (transposition/compliance tracking) and when not to (regulations/decisions; directive itself via other tools). It also clarifies the optional country filter and the language field's non-translation caveat.

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

Deploy Server

Other Tools