InspireHEP MCP Server

Get Citations

get_citations

Read-onlyIdempotent

Retrieve a paper's citation graph from InspireHEP. Choose citing or cited-by direction to get citation lists, metadata, total count, and yearly timeline.

Instructions

Retrieve citation graph data for a paper.

Args: inspire_id: InspireHEP record ID (numeric). direction: "citing" (papers that cite this) or "cited_by" (papers this cites). size: Number of results to return (1–250, default 50).

Returns citation list with metadata, total count, and a year-by-year citation timeline.

Input Schema

TableJSON Schema

Name	Required	Default
`size`	No
`direction`	No	citing
`inspire_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.3.0Sep 8, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"get_citationsOutput"New value: +"get_citationsDictOutput"

First observedv0.1.4Jun 11, 2026

TDQS

A4.4/5.0

Behavior3/5

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

The annotations already declare read-only and idempotent behavior, which the description does not contradict. The description adds a brief note about the return format (citation list, metadata, count, timeline), but this is more about output than behavioral traits. With the annotations covering safety, the description adds only marginal behavioral context.

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 well-structured with an 'Args' section and a 'Returns' section, front-loading the core purpose. It is concise without unnecessary fluff, and each sentence serves a clear informative purpose.

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?

The tool is simple with three parameters, and the description explains all of them along with the return shape. Since an output schema exists, the summary of the return is sufficient context. No critical usage information is missing.

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

Parameters5/5

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

The description adds substantial meaning to each parameter beyond the raw schema. It explains that inspire_id is a numeric record ID, defines the two valid values for 'direction', and clarifies that size is a result count with a range and default. This greatly aids correct invocation.

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 tool's purpose with a specific verb ('Retrieve') and resource ('citation graph data for a paper'). It is distinct from sibling tools like 'get_references' or 'get_paper_details' by focusing on citation graphs, making its 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 Guidelines4/5

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

The description provides clear context on what the tool does and explains the parameters, especially the 'direction' option (citing vs cited_by). However, it does not explicitly mention when to use it instead of related tools like 'get_references', so it lacks explicit alternative guidance.

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

Deploy Server