InspireHEP MCP Server

Get BibTeX

get_bibtex

Read-onlyIdempotent

Retrieve a paper's BibTeX citation by entering any common identifier: DOI, arXiv ID, or InspireHEP record ID.

Instructions

Retrieve the BibTeX citation entry for a paper.

Accepts any common identifier format:

Inspire ID: "3456"
arXiv ID: "arxiv:2301.12345", "arxiv:hep-ph/0123456", or full URL
DOI: "10.1103/PhysRevLett.123.456789" or full URL

Args: identifier: A DOI, arXiv ID, or InspireHEP record ID.

Returns the BibTeX entry along with paper title, texkey, and the resolved Inspire record ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`identifier`	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_bibtexOutput"New value: +"get_bibtexDictOutput"

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?

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds behavioral context by specifying the return payload (BibTeX, paper title, texkey, resolved Inspire record ID) and clarifying accepted identifier formats. It does not contradict annotations and provides useful detail beyond them.

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-organized: a one-sentence purpose statement, a bulleted list of accepted formats, and a separate Args section. It is front-loaded with the core function and avoids verbosity. Every sentence contributes value, and the format is scannable for an agent.

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 a single required parameter, and an output schema exists (as indicated by context signals). The description covers the input formats and the return contents, leaving nothing essential missing. The presence of an output schema means return values don't need further elaboration.

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 only a bare 'identifier' string with no description, leaving 0% schema coverage. The description fully compensates by detailing the three accepted identifier formats and giving concrete examples for each. This adds meaning that the schema lacks entirely.

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: 'Retrieve the BibTeX citation entry for a paper.' It specifies a concrete verb and resource, and the accepted identifier formats (Inspire ID, arXiv ID, DOI) make it distinct from sibling tools like search_papers or get_paper_details. No ambiguity about what it does.

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 usage—when you need a BibTeX entry—but it does not explicitly compare itself to alternatives or state when not to use it. It does not mention that get_citations or get_paper_details might be better for other needs. The guidance is functional but not explicit about selection criteria.

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

Deploy Server