inspirehep-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspirehep_search_by_titleB | Search INSPIRE-HEP literature by title. |
| inspirehep_search_by_fulltextA | Search INSPIRE-HEP literature by full text. |
| inspirehep_search_by_authorC | Search INSPIRE-HEP literature by author. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: searching by author, full text, or title. There is no overlap in functionality, and an agent can easily tell them apart based on the search parameter.
All tool names follow a consistent pattern: 'inspirehep_search_by_' followed by the search parameter (author, fulltext, title). This verb_noun structure is uniform and predictable throughout the set.
With only 3 tools, the server feels thin for a literature search domain. While the tools cover basic search methods, the scope is limited, and more operations (e.g., filtering, sorting, or retrieving specific records) might be expected for a comprehensive search interface.
The tool surface is severely incomplete for a literature search server. It only offers search functionality without any way to retrieve, update, or manage records (e.g., get_by_id, list_results, or advanced filtering). This creates significant gaps that could lead to agent failures when trying to perform full workflows.