Skip to main content
Glama

eurlex_summary

Read-onlyIdempotent

Retrieves official plain-language LEGISSUM summaries of EU legal acts by CELEX identifier, providing non-technical overview in any EU language.

Instructions

Returns the EU's official plain-language summary (LEGISSUM) of a legal act — a short editorial overview written for non-lawyers ("what is the aim", "key points", "from when does it apply"), NOT the binding legal text. Input is the act's celex_id (e.g. "32016R0679" for the GDPR, "32022R2065" for the Digital Services Act) and a language (any of the 24 official EU languages; summaries are usually available in all of them). Output is the summary text (plain, HTML stripped) plus its LEGISSUM id, title, last-update date, an obsolete flag, and source_url (the EUR-Lex summary page). Long summaries paginate via max_chars/offset exactly like eurlex_fetch — pass the previous response's next_offset to continue. Several thousand major acts have a summary; many acts have none (you get a clear "no summary" message). When an act has several summaries the most current non-obsolete one is returned and the rest are listed in other_summaries. For the full legal text use eurlex_fetch; for structured metadata use eurlex_metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoCharacter offset for pagination (0-based)
celex_idYesCELEX identifier of the EU act to summarize, e.g. "32016R0679" (GDPR) or "32022R2065" (Digital Services Act). LEGISSUM summaries exist for several thousand major acts; many acts have none.
languageNoLanguage of the summary text, as a Cellar 3-letter code (any of the 24 official EU languages, e.g. DEU, ENG, FRA, POL, SPA). Summaries are typically available in all 24 languages.ENG
max_charsNoMaximum number of characters returned

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoISO date of the returned summary, or ''
titleNo
offsetNoThe offset this window was sliced from
contentNoSummary text (plain, HTML stripped), sliced to window
celex_idYesThe act CELEX that was queried
languageYes
obsoleteNoTrue when the returned summary is flagged obsolete
truncatedNoTrue when more content remains beyond this window
source_urlNoEUR-Lex legislative-summary (LSU) page for the act
legissum_idNoLEGISSUM id of the returned (primary) summary
next_offsetNoOffset to request next, or null when there is no more content
total_charsNoLength of the full processed summary
returned_charsNoLength of `content`
other_summariesNoOther summaries for the same act (present only when total_summaries > 1)
total_summariesYesTotal LEGISSUM summaries linked to this act; 0 means none was found
Behavior5/5

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

Adds substantial context beyond annotations: pagination behavior, obsolete flag, multiple summary handling, non-binding nature, and that summaries are available in all 24 languages. No contradictions 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?

Every sentence serves a purpose; front-loaded with main action, followed by input, output, pagination, edge cases. No wasted words.

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 aspects: input, output, pagination, edge cases (no summary, multiple summaries), and sibling differentiation. Output schema exists so return values need no additional explanation.

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. Description adds value with concrete examples (GDPR, DSA), explains Cellar 3-letter codes, and clarifies pagination, but few additional details beyond 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 the tool returns a plain-language summary (LEGISSUM) of an EU act, distinguishes from siblings like eurlex_fetch and eurlex_metadata, and provides specific verb-resource combination.

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 tells when to use (to get summary) and when not (for full legal text or metadata), including alternatives. Also notes that many acts have no summary and explains pagination.

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