Skip to main content
Glama
Sign In
LexAPI MCP

LexAPI MCP

Official
by Lex-API
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lex_citation_network

Retrieve inbound and outbound citations for any EU legal document (CELEX) with per-edge-type counts to understand its citation context.

Instructions

Fetch both inbound and outbound citations for a CELEX in one call, with per-edge-type counts. Use when the user wants a holistic view of how a document sits in the citation graph.

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_citation_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
celexNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description bears full burden. It states it fetches citations with counts, implying a read operation, but does not disclose details like error handling, rate limits, or what happens if the CELEX is not found. It is adequate but not comprehensive.

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 two sentences, front-loading the key action and result. No extraneous words, every sentence adds value.

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?

For a tool with one parameter, no annotations, and no output schema, the description provides the essential information: what it does, when to use it, and what it returns (citations with counts). Could mention pagination or limits but is largely complete.

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 0%, so the description must compensate. The single parameter 'celexNumber' is explained by context ('for a CELEX'), and the description clarifies its role. It could specify the format but is sufficient for understanding.

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 action ('fetch'), the resource ('citations for a CELEX'), and the scope ('both inbound and outbound in one call'). It also mentions per-edge-type counts, distinguishing it from sibling tools like lex_cited_by and lex_cites.

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?

The description gives a clear use case ('when the user wants a holistic view of how a document sits in the citation graph'). It implicitly contrasts with directional siblings but does not explicitly state when not to use it or provide alternatives.

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