InspireHEP MCP Server

Get References

get_references

Read-onlyIdempotent

Generates a formatted reference list for a paper from an InspireHEP record ID, with output in BibTeX, JSON, LaTeX, or Eu formats. Returns the references, total count, and paper title.

Instructions

Generate a formatted reference list for a paper.

Args: inspire_id: InspireHEP record ID (numeric). format: Output format — "bibtex", "json", "latex-us", or "latex-eu".

Returns the reference list in the requested format along with total reference count and paper title.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No		bibtex
`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_referencesOutput"New value: +"get_referencesDictOutput"

First observedv0.1.4Jun 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The readOnlyHint and idempotentHint annotations cover side effects, and the description adds what is returned (reference list, total count, paper title). It does not mention error behavior, but that is not required given annotations.

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 compact and front-loaded with the core purpose in the first sentence. The parameter explanations and return summary add necessary detail without padding.

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 two-parameter read-only tool, the description covers inputs and return shape, and an output schema exists. It could slightly clarify how get_references differs from the sibling get_bibtex, but overall it is sufficiently complete.

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?

Although schema descriptions are absent, the description fully explains inspire_id as a numeric InspireHEP record ID and format with all allowed output values. This provides more meaning than the bare 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?

States a specific action: generate a formatted reference list for a paper. It is distinct enough from siblings like get_paper_details and get_bibtex, although it does not explicitly say it returns the works cited by the paper.

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 implies when to use the tool based on the need for a paper's reference list, but it does not explicitly compare or exclude sibling tools such as get_bibtex. No explicit when-to-use/when-not-to-use guidance is provided.

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

Deploy Server