Skip to main content
Glama
Sign In
Honeyfield-Org

eurlex-mcp-server

by Honeyfield-Org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

eurlex_citations

Read-onlyIdempotent

Retrieves citation relationships for an EU legal act by CELEX ID, including cites, cited_by, amendments, legal bases and repeals.

Instructions

Finds citation relationships for an EU legal act: cites, cited_by, amends/amended_by, based_on/basis_for, repeals/repealed_by. direction="both" runs a balanced split so recent cited_by entries cannot crowd out cites results; the response's counts field reports how many of each side were found. The limit is divided evenly between the two directions and is not back-filled from the richer side, so direction="both" can return fewer than limit total results even when one side has more matches available.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results
celex_idYesCELEX identifier, e.g. '32024R1689'
languageNoLanguage of the title, as a Cellar 3-letter code (any of the 24 official EU languages, e.g. DEU, ENG, FRA, POL, SPA)ENG
directionNoDirection: cites=acts referenced by this document, cited_by=acts referencing this document, both=a balanced split of both directionsboth

Output Schema

NameRequiredDescriptionDefault
totalYesNumber of entries in `citations`
countsYesHow the returned citations split across the two directions
celex_idYesThe act whose citations were queried
citationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.4.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / counts / properties / cited_by / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / counts / properties / cited_by / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / counts / properties / cites / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / counts / properties / cites / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / total / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / total / minimum
      Added value: +-9007199254740991
  2. Addedv2.4.2
  3. Removedv2.3.0
  4. First observedv2.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds meaningful behavioral detail beyond that: direction="both" splits the limit evenly, does not back-fill from the richer side, and may return fewer than limit results, with a counts field reporting each side.

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 front-loaded with purpose and relationship types, followed by the non-obvious balanced-split caveat. Both sentences earn their place and there is no filler.

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 full schema coverage, annotations covering safety, and an output schema, the description is complete enough to invoke correctly. It additionally explains the subtle result-count behavior that an agent would otherwise miss.

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 description coverage is 100%, so the schema already documents all four parameters. The description adds real meaning for direction and its interaction with limit, especially the non-obvious balanced split behavior, though it does not elaborate on celex_id or language beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it finds citation relationships for an EU legal act, and it enumerates the relationship types. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as eurlex_fetch or eurlex_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the direction values and the balanced behavior of direction="both", which helps an agent choose parameters. However, it does not explicitly say when to use this tool versus sibling tools or when not to use it, so usage guidance is implied rather than stated.

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