Skip to main content
Glama

eurlex_transposition

Read-onlyIdempotent

Retrieve national transposition measures for any EU directive by CELEX ID, optionally filtered by member state, for compliance tracking.

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
Behavior5/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. The description adds that results are capped at limit, total_found reports full count, titles are in original language, and language only affects URL locale. It also notes that member states transpose directives only.

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

Conciseness4/5

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

The description is a single paragraph with 4-5 sentences covering essential points without fluff. It could be more structured (e.g., separating input/output) but is still efficient and front-loaded.

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 complexity (4 params, output schema exists), the description provides a thorough overview: it mentions response fields (member state, title, date, CELEX, URL, total_found, results capped), differentiates from siblings, and covers key constraints (titles not translated, directives only). It is complete for an agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for all parameters. The description adds useful context: celex_id must be sector-3 CELEX for directives, country codes are ISO 3166-1 alpha-2 with Greece as 'EL', and language does not translate titles. This goes beyond baseline 3.

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 it lists national implementing measures for EU directives, specifies the input (celex_id for directives), and differentiates from siblings by noting that for the directive itself one should use eurlex_fetch/eurlex_metadata and that regulations/decisions have no NIMs.

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 says when to use (transposition/compliance tracking) and when not to (directive itself, regulations/decisions). Also mentions optional country filtering and the purpose of the language parameter.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Honeyfield-Org/eurlex-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server