InspireHEP MCP Server

Get Author Papers

get_author_papers

Read-onlyIdempotent

Retrieve an author's publication list and citation metrics, including total citations, h-index, and average citations per paper, by name or InspireHEP ID. Sort results by recency or citation count.

Instructions

Retrieve publication history and citation metrics for an author.

Provide either author_name or author_id:

author_name: "Weinberg, Steven" (Last, First format)
author_id: "S.Weinberg.1" (InspireHEP BAI)

Returns a list of papers plus aggregate metrics including total citations, h-index, and average citations per paper.

Args: author_name: Author name in "Last, First" format. author_id: InspireHEP author identifier (BAI). sort: Sort order — "mostrecent" or "mostcited". size: Number of papers to return (1-100, default 20).

Input Schema

TableJSON Schema

Name	Required	Default
`size`	No
`sort`	No	mostrecent
`author_id`	No
`author_name`	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_author_papersOutput"New value: +"get_author_papersDictOutput"

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 annotations already indicate readOnly and idempotent behavior, and the description is consistent with that. It adds useful behavioral details such as returning aggregate metrics (total citations, h-index, average citations) and the paper list, while not contradicting 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?

The description is well-structured with an intro and an Args block, but it repeats author_name and author_id details in prose and again in the Args list. This minor redundancy is not harmful but prevents a perfect conciseness score.

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?

With all parameters described and return values summarized, the description is sufficient for typical usage. It does not specify behavior when both author_name and author_id are omitted or both provided, but this is a minor gap given the clear parameter guidance.

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?

Although the input schema has no per-parameter descriptions, the tool description explains all four parameters: author_name (format), author_id (BAI format), sort (allowed values), and size (range and default). This fully compensates for the schema's lack of descriptions.

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 a specific action ('Retrieve publication history and citation metrics for an author') and identifies the resource (an author). This distinguishes it from sibling tools like search_papers or get_paper_details, which have different scopes.

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 provides clear context for when to use the tool: retrieving papers and metrics for a specific author. It also explains how to supply the author (either by name or BAI) and includes sort/size options. It does not explicitly compare against sibling tools, but the usage context is clear.

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

Deploy Server