InspireHEP MCP Server

Get Paper Figures

get_paper_figures

Read-onlyIdempotent

Retrieve figures and captions from a scientific paper using its arXiv ID, DOI, or Inspire ID. Get direct download links for each figure.

Instructions

Retrieve figures for a specific paper.

Provide at least one identifier. Accepts multiple formats:

inspire_id: "3456"
arxiv_id: "arxiv:2301.12345", "arxiv:hep-ph/0123456", or full URL
doi: "10.1103/PhysRevLett.123.456789" or full URL

Returns title, inspire url, and a list of figures with their captions, descriptions and direct download URLs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`doi`	No
`arxiv_id`	No
`inspire_id`	No

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_paper_figuresOutput"New value: +"get_paper_figuresDictOutput"

First observedv0.1.4Jun 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The readOnlyHint and idempotentHint annotations already cover side-effect expectations. The description adds useful behavioral context by specifying the required identifier condition and the shape of the returned data, though it does not discuss error cases if no identifier is provided.

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 concise, well-structured, and free of unnecessary detail. The identifier formats are presented as a clear bullet list, and the return value summary is direct.

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 description is complete enough for a low-complexity tool. It covers all three parameters, explains the identifier requirement, and describes the output despite the presence of an output schema. No critical usage context 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 input schema provides no descriptions for the parameters, but the description compensates fully by explaining the accepted formats for doi, arxiv_id, and inspire_id, including concrete examples and the requirement to provide at least one identifier.

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 that the tool retrieves figures for a specific paper and lists the returned data (title, INSPIRE URL, figures with captions/descriptions/download URLs). This is specific enough to distinguish it from sibling tools like get_paper_details or search_papers.

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 gives good input guidance by explaining identifier formats and requiring at least one identifier, but it does not explicitly say when to prefer this tool over alternatives or when not to use it. The usage is implied rather than directly contrasted with sibling tools.

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

Deploy Server