Skip to main content
Glama

Inspire Hep Author

inspire_hep_author
Read-onlyIdempotent

Author record by INSPIRE id.

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": {
      "record_id": 1001234
    },
    "name": "inspire_hep_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
record_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds no behavioral context at all — nothing about error behavior for unknown ids, coverage, or whether it hits an external service.

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

Conciseness3/5

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

One short phrase with zero filler, so there is nothing to trim, but for a tool with 0% schema coverage and no annotation gaps left to fill, this size is under-specified rather than economical. It is front-loaded but thin.

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

Completeness2/5

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

An output schema exists, so return values need not be described, and annotations cover safety. Still, with an undocumented required parameter and no differentiation from lookalike author/search tools in the sibling set, the definition leaves the agent guessing at both invocation details and tool choice.

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 load; "INSPIRE id" does clarify that record_id is an INSPIRE author identifier rather than an internal one, and the schema example shows numeric form. However, it gives no format details, range, or what happens with a non-author id, leaving the single required parameter only partially specified.

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

Purpose3/5

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

"Author record by INSPIRE id" names the resource (INSPIRE author record) and the key (INSPIRE id), but it is a noun phrase with no verb, so the agent must infer that this is a lookup/retrieval. It does not distinguish the tool from siblings like authors_search or entity_profile, which an agent could plausibly pick instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "by INSPIRE id" weakly implies the precondition that you already hold an INSPIRE author id, but there is no explicit when-to-use, when-not-to-use, or named alternative. Nothing tells the agent whether to prefer this over authors_search when starting from a name.

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.