eurlex-mcp-server

eurlex_fetch

Read-onlyIdempotent

Retrieve the full text of an EU legal act using a CELEX ID, ELI, or Official Journal reference. Supports pagination, language selection, and multiple output formats.

Instructions

Fetches the full text of an EU legal act. Identify it by celex_id (e.g. "32024R1689"), by eli (e.g. "reg/2016/679" or a full ELI URL), or by oj_ref (post-2023 Official Journal reference, e.g. "OJ:L_202401689") — provide exactly one. Paginate long documents with offset and max_chars: pass the previous response's next_offset to continue reading until it is null.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`eli`	No	European Legislation Identifier (ELI), short or full form, e.g. "reg/2016/679" or "http://data.europa.eu/eli/reg/2016/679/oj" (GDPR). Resolved to a CELEX ID via Cellar. Provide exactly one of celex_id, eli, or oj_ref.
`format`	No	Output format: xhtml=structured XHTML, plain=text with XHTML tags stripped	xhtml
`offset`	No	Character offset for pagination (0-based)
`oj_ref`	No	Official Journal reference in the post-2023 scheme, e.g. "OJ:L_202401689" (AI Act). Resolved to a CELEX ID via Cellar. Provide exactly one of celex_id, eli, or oj_ref.
`celex_id`	No	CELEX identifier, e.g. "32024R1689" (AI Act). Provide exactly one of celex_id, eli, or oj_ref.
`language`	No	Language of the full text, as a Cellar 3-letter code (any of the 24 official EU languages, e.g. DEU, ENG, FRA, POL, SPA)	ENG
`max_chars`	No	Maximum number of characters returned

Output Schema

TableJSON Schema

Name	Required	Description
`offset`	Yes	The offset this window was sliced from
`content`	Yes	The document text in the requested window/format
`celex_id`	Yes	The resolved CELEX ID the text was fetched for
`language`	Yes	Cellar 3-letter language code of the text
`truncated`	Yes	True when more text remains beyond this window
`source_url`	Yes	Cellar REST URL of the fetched resource
`next_offset`	Yes	Offset to request next, or null when there is no more content
`total_chars`	Yes	Length of the full processed document
`returned_chars`	Yes	Length of `content`

Tool Definition Quality

A4.2/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. The description adds context about pagination behavior and identifier resolution via Cellar, but does not disclose other traits like rate limits or return format details beyond the schema.

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 one paragraph of four sentences, front-loaded with purpose, then identifier options, then pagination. Every sentence is necessary and there is no redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, pagination, output schema exists), the description covers identification and pagination well. It does not detail the language parameter or format options, but those are covered in schema. Missing explicit mention of full-text scope (already clear from purpose).

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%, so baseline is 3. The description adds meaning by explaining the exclusive OR relationship among celex_id, eli, and oj_ref, and the pagination flow with next_offset, which goes beyond individual parameter descriptions.

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 uses a specific verb ('Fetches the full text') and resource ('EU legal act'), and clearly distinguishes from siblings like eurlex_summary or eurlex_structure by emphasizing full text retrieval and multiple identifier options.

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 states 'provide exactly one' of the identifiers and gives examples for each. It also explains pagination with offset and max_chars, linking to next_offset. However, it does not explicitly exclude usage in favor of sibling tools.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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