Skip to main content
Glama

Pandex

Citations of an article or a decision

get_citations
Read-onlyIdempotent

What cites a document or one of its articles (direction "in": the leading ones first, those the other citing documents cite most, each with the passage that cites it), or what it cites (direction "out"), with the places where. Targets we do not hold are listed as written. To search inside the citing passages, use search with cites.

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": {
      "id": "<id>"
    },
    "name": "get_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from a result, or an identifier or citation.
limitNoLines to return, 1–60. Default 15.
orderNoFor direction in. leading (default): those the other citing documents cite most. newest: by date.
elementNoOnly citations of, or from, this element.
relationNoOnly one relation: cites, amends, repeals, implements, consolidates, appeals, joins.
directionNoin (default): documents that cite it. out: what it cites.
max_tokensNoSize of the answer in tokens, 200–8000. Default 1500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: results carry the citing passage and the places, and 'Targets we do not hold are listed as written' — a quirk an agent would otherwise misread as an error. It does not mention truncation against max_tokens, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core question (what cites / what it cites) before the parenthetical detail, and the sibling redirect lands last where it belongs. The nested parenthetical around direction 'in' is dense and takes a second pass to parse, costing a point.

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?

Seven parameters but a fully documented schema and no output schema, so the description only needs to cover mode selection and return character — which it does. What is missing is how limit/max_tokens interact and whether results are paginated, which matters for a list tool with two size knobs.

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 100%, so the baseline is 3 and the schema already defines every parameter including both enums. The description still contributes: it explains what 'leading' actually produces ('those the other citing documents cite most, each with the passage that cites it'), which clarifies the return shape rather than restating the enum. No detail on element/relation interplay, so not a 5.

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?

States a specific verb+resource pair ('what cites a document or one of its articles' / 'what it cites') and immediately disambiguates the two modes via the direction values. An agent can distinguish this from search or get_document without opening the schema.

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?

Explicitly routes one adjacent case to a sibling: 'To search inside the citing passages, use search with cites.' That is a real when-to-use-else signal. It does not cover the other plausible alternatives (get_document, get_outline, list_sources), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources