Skip to main content
Glama

eurlex_summary

Read-onlyIdempotent

Retrieves the official plain-language summary of an EU legal act by CELEX ID and language, with pagination support.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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#"
  2. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / language / default
      Previous value: -"DEU"New value: +"ENG"
  3. First observedv2.2.0

TDQS

A5/5.0
Behavior5/5

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

The description aligns with the annotations (readOnlyHint, idempotentHint, destructiveHint) and adds behavioral details not covered by annotations: pagination behavior ('pass the previous response's next_offset to continue'), selection of the most current summary, and the 'no summary' message. No contradictions.

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 paragraph that leads with purpose, then input/output details, pagination, edge cases, and ends with alternative tools. It contains no redundancy and all information is directly relevant.

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?

The description covers the full context: input format, output contents (summary text, id, title, date, flag, source_url, other_summaries), pagination, edge cases (no summary, multiple summaries), and sibling tools. It is complete for an agent to know when and how to use this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters (celex_id, language, offset, max_chars) are explained in the schema. The description adds semantic layer: celex_id examples, language availability across 24 EU languages, and pagination 'exactly like eurlex_fetch'. This enriches the schema descriptions, which already had 100% coverage.

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 identifies the tool's function: 'Returns the EU's official plain-language summary (LEGISSUM) of a legal act'. It distinguishes this from the binding legal text and explicitly contrasts with sibling tools (eurlex_fetch for full text, eurlex_metadata for metadata), making the purpose unambiguous.

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 provides explicit usage guidance: 'For the full legal text use eurlex_fetch; for structured metadata use eurlex_metadata.' It also explains when no summary is available and that the most current non-obsolete summary is returned, giving clear conditions for use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.