Skip to main content
Glama

Eur Lex

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Document

get_document
Read-onlyIdempotent

Plain-text of a whole act (recitals + enacting terms), paged. Use for short acts or to read recitals/definitions; for a specific Article prefer get_article. Returns up to max_chars from offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoISO 639-2/B language code (default "eng").
celexYesCELEX id or a known alias.
offsetNoCharacter offset to start from, for paging (default 0).
max_charsNoMax characters to return (default 8000, max 40000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "celex": "GDPR"
+  },
+  {
+    "celex": "32022R0868",
+    "max_chars": 16000,
+    "offset": 0
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds context that the tool returns plain-text, includes recitals/enacting terms, and supports paging via offset/max_chars. 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?

The description is a single dense sentence that conveys purpose, scope, alternatives, and paging behavior without any wasted words. Front-loaded with key information.

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?

No output schema, but the description explains return type (plain-text of whole act) and paging constraints. Annotations cover safety. Could mention error handling or encoding, but adequate for this level of complexity.

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

Parameters3/5

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

Schema coverage is 100% with detailed parameter descriptions (lang, celex, offset, max_chars). The description mentions max_chars and offset in context, but does not add new semantic information beyond what the schema provides. Baseline score of 3 is appropriate.

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 returns the plain-text of a whole act (recitals + enacting terms) with paging. It distinguishes itself from the sibling get_article by specifying that get_article is for a specific Article, 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?

Explicitly states when to use this tool: 'Use for short acts or to read recitals/definitions' and when to use the alternative: 'for a specific Article prefer get_article'. This provides clear guidance on tool selection.

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

All Eur Lex toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources