Skip to main content
Glama
Sign In
LexAPI MCP

LexAPI MCP

Official
by Lex-API
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lex_get_document

Fetch the full parsed content of an EU document by CELEX number, including metadata and structured body with articles, sections, and tables.

Instructions

Fetch the full parsed content of a single EU document by CELEX number. Returns metadata (title, type, dates, author, ECLI/ELI, keywords) plus structured body (articles, sections, tables, annexes). Articles are individually addressable with id, number, title, and content. Use this when the user has a specific CELEX or wants the body of a known document.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "celexNumber": "<celexNumber>"
    },
    "name": "lex_get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
celexNumberYesCELEX identifier, e.g. 32016R0679 for the GDPR.
bypassCorpusNoForce a fresh live fetch instead of the cached copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses return structure comprehensively: metadata fields and structured body with articles, sections, etc. Mentions the 'bypassCorpus' parameter for fresh fetch. Lacks minor details like error handling or rate limits.

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?

Extremely concise at two sentences. First sentence states purpose and output clearly. Second sentence provides usage guidance. No unnecessary words; front-loaded with key information.

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?

For a simple retrieval tool with 2 parameters and no output schema, the description is complete. It explains what it does, when to use it, and what it returns in detail. No gaps for typical use cases.

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 description coverage is 100% with clear descriptions for both parameters. The description adds context (e.g., 'by CELEX number') but does not significantly extend beyond the schema. Baseline 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?

Description clearly states 'Fetch the full parsed content of a single EU document by CELEX number.' It specifies the verb (Fetch), resource (full parsed content), and method (CELEX number). Differentiates from siblings like 'lex_get_metadata' and 'lex_get_document_by_url' by focusing on full document retrieval by CELEX.

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?

Provides explicit usage guidance: 'Use this when the user has a specific CELEX or wants the body of a known document.' However, it does not explicitly state when not to use it or mention alternatives (though sibling names imply them).

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

Deploy Server

Other Tools