Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Maldacena"
    },
    "name": "authors_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive semantics, so the description is free to add real context. It does: the query dialect (Lucene/Solr) and the fact that a bare surname or an ORCID both work, plus the shape of the returned fields. It omits caveats an agent would want, such as behavior on ambiguous or common names, result caps, and how size defaults are applied.

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 front-loaded sentences that move from what it searches, to how to query it, to what comes back. The final 'Answers which...' sentence partly restates the return-fields sentence, a small redundancy, but overall it is tightly written with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so enumerating return fields is generous but not strictly required, and the description is otherwise adequate for a simple 2-parameter search. The gap is 'size': with 0% schema coverage and no mention in text, an agent cannot know whether it is a result limit, page size, or has a default.

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?

Schema description coverage is 0%, so the description must carry the burden; it partially does by explaining that 'query' is a Lucene/Solr expression accepting a surname or ORCID. The second parameter 'size' is never mentioned anywhere, leaving its meaning and default undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: search INSPIRE-HEP HEPNames author records, and it names the answerable question (which physicist a name refers to, and their record id). It implicitly separates itself from literature search by scoping to author records, but never explicitly contrasts with the sibling inspire_hep_author, so an agent must infer search-vs-lookup.

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?

Usage is implied rather than stated: the phrase 'Answers which particle physicist a name refers to' suggests a name-disambiguation use case. There is no explicit when-to-use, when-not-to-use, or routing to inspire_hep_author / inspire_hep_search for alternative needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.