OpenPapers

Get paper

get_paper

Retrieve a canonical research paper by providing its paper ID, DOI, or arXiv ID.

Instructions

Retrieve a canonical research work by paper ID, DOI, or arXiv ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paper_id": "<paper_id>"
    },
    "name": "get_paper"
  }
}

Input Schema

Name	Required	Description	Default
`paper_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of explaining behavior. It states that the operation is a retrieval, but does not disclose what exactly is returned, how 'canonical' is determined, error behavior for unknown IDs, or any other runtime details. This is a significant gap for a standalone tool definition.

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

Conciseness5/5

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

The description is a single, front-loaded sentence. Every word contributes: the verb, the resource type, and the acceptable identifier formats. There is no redundancy or 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?

For a simple one-parameter retrieval tool, the description is minimally viable. It defines the core action and the input, but without an output schema or annotations it does not explain the return value, which is a notable gap for an agent deciding whether to use this tool instead of get_bibtex, read_paper, or search_papers.

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

Parameters4/5

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

With only one parameter and 0% schema description coverage, the description compensates well by clarifying that paper_id can be a paper ID, DOI, or arXiv ID. This gives the agent meaningful guidance beyond the plain string type in the schema, though exact format examples are not provided.

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?

The description uses a specific verb ('retrieve') and a clear resource ('canonical research work'), and specifies the identifier types accepted. It is not a tautology and provides enough detail to distinguish it from search-oriented siblings, though it does not name them explicitly.

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?

The description implies when to use the tool: when you already have a paper ID, DOI, or arXiv ID. However, it does not explicitly say when not to use it or point to alternatives like search_papers or read_paper, leaving some inference to the agent.

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