Semantic Scholar MCP Server

get_paper

Retrieve detailed information about a specific academic paper using any supported identifier such as DOI, ArXiv ID, or PubMed ID. Access abstracts, authors, citations, and metadata in one query.

Instructions

Get detailed information about a specific paper.

Args: paper_id: Semantic Scholar paper ID, DOI, ArXiv ID (prefix with "ArXiv:"), CorpusId (prefix with "CorpusId:"), PMID, ACL ID, or a URL.

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. It only says 'Get' and lists ID formats, which are input constraints rather than behavioral context. It does not state read-only status, rate limits, coverage, or what 'detailed information' includes beyond what an output schema would show.

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 short, front-loaded with the tool's purpose, and every line earns its place. The Args section packs all identifier variants into a compact format without redundant prose.

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 a single required parameter, an existing output schema, and full identifier enumeraton, the description is nearly complete for a simple lookup tool. It would improve from a brief note routing users to search_papers when no identifier is available or any behavioral caveats.

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?

The schema provides no description for paper_id, but the Args block fully compensates by enumeratting all accepted formats: Semantic Scholar paper ID, DOI, ArXiv, CorpusId, PMID, ACL ID, and URL. This gives the agent the exact input semantics needed to invoke the tool correctly.

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 clear verb-resource pair ('Get detailed information about a specific paper'). It distinguishes the tool from search-oriented siblings at a basic level, but does not explicitly contrast it with get_citations or get_references.

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 accepted identifier list implies this tool is for lookups when you already have a paper ID or URL. It does not explicitly guide the agent toward search_papers when no ID is available, nor does it describe when not to use this tool.

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

Deploy Server