Inspire Hep

Authors Search

authors_search

Read-onlyIdempotent

INSPIRE-HEP, the high-energy-physics literature database — search its HEPNames author records with a Lucene/Solr query such as a surname or ORCID. Returns each author's INSPIRE record id, preferred and alternative name forms, institutional affiliations, ORCID and arXiv categories. Answers which particle physicist a name refers to in INSPIRE and what their author record id is.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`size`	No
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Maldacena"
+  },
+  {
+    "query": "Witten",
+    "size": 10
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results from INSPIRE-HEP authors API",
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare the tool read-only and idempotent. The description adds the types of queries accepted and the fields returned (e.g., record id, ORCID, affiliations). It does not mention pagination or rate limits, so it adds some but not extensive behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each adding value—context, return values, and purpose. The description is front-loaded and free of verbose filler, though the opening appositive could be trimmed slightly.

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 covers the tool's purpose, query format, and return fields. With an output schema present and only two parameters (one explained), the description is adequate for correct invocation, though the 'size' parameter remains a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The explanation of 'query' as a Lucene/Solr query with examples (surname or ORCID) adds meaningful semantics beyond the bare string type. However, 'size' is left undefined with no guidance on maximum values or default behavior.

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 explicitly states 'search its HEPNames author records with a Lucene/Solr query such as a surname or ORCID,' which clearly identifies the action (search) and resource (author records). It also specifies the output (record id, name forms, affiliations, ORCID, arXiv categories), distinguishing it from sibling search tools.

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?

It states the tool 'answers which particle physicist a name refers to in INSPIRE and what their author record id is,' giving clear context for when to use this tool. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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

All Inspire Hep tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.