Skip to main content
Glama

eurlex_consolidated

Read-onlyIdempotent

Fetch the latest consolidated text of an EU legal act with all amendments merged. Identify by CELEX ID or document type, year, and number.

Instructions

Fetches the latest consolidated (currently in-force) version of an EU legal act via ELI, with all amendments merged in. Identify the act with celex_id (e.g. "32016R0679") OR with doc_type + year + number — provide exactly one of the two. celex_id must be a sector-3 secondary-law CELEX (3YYYY[R|L|D]NNNN).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoYear of the act, e.g. 2024. Required together with doc_type and number when celex_id is not used.
formatNoOutput format: xhtml=structured XHTML, plain=text with XHTML tags strippedxhtml
numberNoDocument number, e.g. 1689. Required together with doc_type and year when celex_id is not used.
offsetNoCharacter offset for pagination (0-based)
celex_idNoCELEX ID of the original act, e.g. "32016R0679" (GDPR). Alternative to doc_type + year + number — provide exactly one of the two input forms. Must be a sector-3 secondary-law CELEX (pattern 3YYYY[R|L|D]NNNN).
doc_typeNoDocument type: reg=regulation, dir=directive, dec=decision. Alternative to celex_id — provide together with year and number.
languageNoLanguage of the returned text, as a Cellar 3-letter code (any of the 24 official EU languages, e.g. DEU, ENG, FRA, POL, SPA)DEU
max_charsNoMaximum number of characters returned

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes
numberYes
offsetYesThe offset this window was sliced from
contentYesThe consolidated text in the requested window/format
eli_urlYesELI URL of the consolidated act
doc_typeYes
languageYes
truncatedYesTrue when more text remains beyond this window
next_offsetYesOffset to request next, or null when there is no more content
total_charsYesLength of the full processed document
returned_charsYesLength of `content`
consolidated_celexYesResolved consolidated CELEX, e.g. "02016R0679-20160504"
consolidation_dateYesISO date from the CELEX "-YYYYMMDD" suffix, or null when absent
Behavior4/5

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

Annotations indicate readOnlyHint, idempotentHint, and no destructiveHint. The description adds behavioral context: it returns the latest consolidated version with all amendments merged. This goes beyond annotations by clarifying the nature of the returned document. No contradiction with 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 concise (3 sentences) and front-loads the core purpose. Each sentence adds essential information: purpose, identification methods, and a specific constraint on celex_id. No filler or redundancy.

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 of 8 parameters with 100% schema coverage and the existence of an output schema, the description is complete. It covers the critical aspect of alternative inputs and the celex_id format. The output schema handles return values, so no further description needed.

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. The description adds value by explaining the alternative input forms (celex_id OR doc_type+year+number) and specifying that celex_id must be a sector-3 secondary-law CELEX pattern, which is more precise than the generic regex in the 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 it fetches the latest consolidated version of an EU legal act via ELI with all amendments merged. It specifies the resource (consolidated legal act) and action (fetch), and distinguishes from siblings like eurlex_fetch by focusing on the consolidated, in-force version.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides two identification methods (celex_id or doc_type+year+number) and instructs to use exactly one. It does not explicitly mention when not to use this tool, but the context of 'consolidated version' implicitly guides against using it for original or historical versions. Given the sibling list, this is sufficient.

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