Skip to main content
Glama
Sign In
Honeyfield-Org

eurlex-mcp-server

by Honeyfield-Org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

eurlex_transposition

Read-onlyIdempotent

Lists national implementing measures EU member states enacted to transpose a given EU directive, with optional country filters for transposition and 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

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

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. Changed5 schema fields changedv2.4.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / returned / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / returned / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / total_found / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / total_found / minimum
      Added value: +-9007199254740991
  2. 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#"
  3. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / language / default
      Previous value: -"DEU"New value: +"ENG"
  4. First observedv2.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds non-obvious behavioral details: results are capped at limit while total_found reports the full count, and national measure titles are returned in the member state's own official language and are not translated. It does not discuss rate limits or pagination beyond the cap, so it falls short of a 5.

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 front-loaded with the core purpose and then moves through examples, filtering, and return semantics. It is dense and informative, though fairly long; nearly every sentence adds value, but it could be tightened slightly without losing meaning.

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?

Even though an output schema exists, the description explains the key return fields (member state, national measure title, date, sector-7 NIM CELEX, EUR-Lex URL) and the total_found/limit relationship. Combined with the annotations and full schema coverage, an agent has everything needed to invoke and interpret the tool 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 description coverage is 100%, so the schema already documents all four parameters. The description still adds useful meaning: it explains that celex_id must be a sector-3 directive CELEX with examples (NIS2, Data Protection Directive), clarifies the country code convention, and emphasizes that language only affects the eurlex_url locale, not NIM titles.

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 gives a specific verb and resource: it lists national implementing measures enacted to transpose a given EU directive. It also explicitly distinguishes this from eurlex_fetch/eurlex_metadata and notes that regulations and decisions have no NIMs, so an agent can tell exactly what this tool is for.

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?

The description states the use case (transposition and compliance tracking), names the sibling tools to use for the directive itself, and explicitly excludes regulations and decisions. It also explains the optional country filter and says to omit it to return all member states.

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