InspireHEP MCP Server

Search Papers

search_papers

Read-onlyIdempotent

Search InspireHEP's high-energy physics literature using free-text or field-specific queries (author, title, collaboration). Sort results by relevance, recency, or citation count, and control the number returned.

Instructions

Search InspireHEP for papers matching a query.

Supports free-text and field-specific queries such as:

"dark matter direct detection"
"author:ellis title:higgs"
"collaboration:ATLAS supersymmetry"
"find a weinberg and t electroweak"

Args: query: Search query string. sort: Sort order — "bestmatch", "mostrecent", or "mostcited". size: Number of results to return (1-100, default 10).

Input Schema

TableJSON Schema

Name	Required	Default
`size`	No
`sort`	No	bestmatch
`query`	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: -"search_papersOutput"New value: +"search_papersDictOutput"

First observedv0.1.4Jun 11, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint and idempotentHint, so the description does not need to restate those. The description adds no further behavioral details beyond the act of searching, which is consistent with the annotations. No contradictions exist.

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 and well structured: a clear opening sentence, illustrative query examples, and a straightforward argument list. It avoids unnecessary detail and stays focused on actionable information.

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?

The description provides all necessary information for calling the tool: query syntax, sort options, size limits, and defaults. Since an output schema is present, return-value details are not required. Minor omissions such as error behavior or empty-result handling are not significant for this simple search tool.

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, but the tool description fully compensates by explaining query, sort, and size, including allowed sort values, the size range, and defaults. The query examples additionally clarify expected syntax.

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 function: 'Search InspireHEP for papers matching a query.' It provides concrete query examples and distinguishes this general search tool from more specific sibling tools like get_paper_details or get_author_papers.

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 gives useful context by showing supported free-text and field-specific query formats, making it clear when this tool is appropriate. It does not explicitly contrast it with search_by_collaboration or other sibling tools, but the examples and general-purpose framing provide sufficient guidance.

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

Deploy Server