Skip to main content
Glama

eurlex_metadata

Read-onlyIdempotent

Retrieve metadata for EU legal acts including dates, in-force status, authors, legal basis, EuroVoc descriptors, and directory codes by providing a CELEX identifier, ELI, or Official Journal reference.

Instructions

Fetches metadata for an EU legal act: document/entry-into-force/end-of-validity dates, in-force status, authors, legal basis (CELEX IDs of the acts it is based on), EuroVoc descriptors, and directory codes. Identify the act 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eliNoEuropean 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.
oj_refNoOfficial 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_idNoCELEX identifier, e.g. "32024R1689" (AI Act). Provide exactly one of celex_id, eli, or oj_ref.
languageNoLanguage of the title and EuroVoc labels, as a Cellar 3-letter code (any of the 24 official EU languages, e.g. DEU, ENG, FRA, POL, SPA)DEU

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
authorsYes
celex_idYes
in_forceYesIn-force status, or null when unknown
eurlex_urlYes
legal_basisYesCELEX IDs of the acts this act is based on
date_documentYesISO date, or null when absent
resource_typeYes
directory_codesYesDirectory-code entries as "{code}: {label}", or the bare code when unlabelled
eurovoc_conceptsYes
date_transpositionYesISO date, or null when absent
date_end_of_validityYesISO date, or null when absent or the open-ended 9999-12-31 sentinel
date_entry_into_forceYesISO date, or null when absent
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. The description adds specific behavioral details like fetching dates, in-force status, authors, etc., which is consistent and adds value beyond 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 a single, well-structured sentence that front-loads the purpose, followed by clear identifier options. Every sentence serves a purpose with no 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 output schema exists (as indicated), the description fully covers what the tool returns and how to call it, including language options. No gaps remain.

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%, baseline 3. The description adds the crucial constraint that exactly one of celex_id, eli, or oj_ref must be provided, which is not enforced in the schema. This adds meaningful semantic guidance beyond 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 explicitly states it fetches metadata for an EU legal act, listing specific metadata fields (dates, status, authors, etc.). It clearly distinguishes from sibling tools like eurlex_search by focusing on metadata retrieval.

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 provides explicit instructions on how to identify the act using one of three identifiers (celex_id, eli, oj_ref) and states 'provide exactly one.' It does not explicitly compare to sibling tools but the context is clear.

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