Skip to main content
Glama

eurlex_transposition

Read-onlyIdempotent

Lists national implementing measures EU member states enacted to transpose a given directive, with title, date, CELEX reference, and EUR-Lex URL. Filter by country for targeted 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.DEU

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?

Adds behavioral context beyond annotations: results are capped at limit, total_found reported, titles are in original language not translated, language only affects URL. Annotations already indicate readonly/idempotent, so description fills remaining gaps.

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?

Single paragraph, front-loaded with core purpose, every sentence provides necessary detail without redundancy. Efficient and well-structured.

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?

Covers all essential aspects: input, optional filters, what each result contains, pagination info (total_found, limit), and relationship to other tools. Complete for a read-only list tool with output schema.

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?

Despite 100% schema coverage, the description adds meaning: celex_id must be a directive (type L), country uses EU codes (Greece=EL), limit range, language does not translate titles. This is valuable extra context.

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 an EU directive, with specific verb 'lists' and resource 'national implementing measures'. It distinguishes from siblings like eurlex_fetch/eurlex_metadata by noting that for the directive itself, use those tools.

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 (for transposition tracking) and when not to (regulations and decisions have no NIMs; for directive itself use eurlex_fetch/eurlex_metadata). Also explains input format and optional filters.

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