Skip to main content
Glama
FujishigeTemma

semantic-scholar-mcp

get_paper

Retrieve detailed information about a specific academic paper using its ID. Customize returned data with a fields parameter to get only what you need.

Instructions

Get detailed information about a specific paper. Use 'fields' parameter to customize returned data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYesThe following types of IDs are supported: - `<sha>` - a Semantic Scholar ID, e.g. `649def34f8be52c8b66281af98ae884c09aef38b` - `CorpusId:<id>` - a Semantic Scholar numerical ID, e.g. `CorpusId:215416146` - `DOI:<doi>` - a Digital Object Identifier, e.g. `DOI:10.18653/v1/N18-3011` - `ARXIV:<id>` - arXiv.rg, e.g. `ARXIV:2106.15928` - `MAG:<id>` - Microsoft Academic Graph, e.g. `MAG:112218234` - `ACL:<id>` - Association for Computational Linguistics, e.g. `ACL:W12-3903` - `PMID:<id>` - PubMed/Medline, e.g. `PMID:19872477` - `PMCID:<id>` - PubMed Central, e.g. `PMCID:2323736` - `URL:<url>` - URL from one of the sites listed below, e.g. `URL:https://arxiv.org/abs/2106.15928v1` URLs are recognized from the following sites: - semanticscholar.org - arxiv.org - aclweb.org - acm.org - biorxiv.org
fieldsNoA comma-separated list of the fields to be returned. The paperId field is always returned. See the resource 'semantic-scholar://fields/paper' for available fields. Examples: - `title,url` - `title,embedding.specter_v2` - `title,authors,citations.title,citations.abstract` paperId,title,abstract,authors,year,citationCount,referenceCount,fieldsOfStudy,publicationTypes,publicationDate,journal,openAccessPdf
Behavior2/5

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

With no annotations provided, the description carries the full burden for transparency. It states the tool 'get[s] detailed information' but does not disclose potential error cases, return format, rate limits, or authentication needs. The input schema is detailed, but behavioral traits are lacking.

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 consists of two short, front-loaded sentences with no unnecessary words. Every sentence contributes to understanding the tool's purpose and a key feature.

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?

Given the absence of an output schema and annotations, the description should elaborate on what 'detailed information' includes (e.g., fields, structure). It lacks sufficient context about return values and error handling, making it incomplete for agents needing to interpret results.

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 100%, so the schema already explains both parameters. The description adds minor value by mentioning the 'fields' parameter for customization, but it does not provide additional semantics beyond what the schema offers.

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 the tool's purpose: 'Get detailed information about a specific paper.' It also mentions a key parameter for customization, distinguishing it from siblings like 'search_paper' (for searching) and 'get_authors' (for authors).

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 advises using the 'fields' parameter to customize data, which is helpful. However, it does not provide explicit guidance on when to use this tool versus alternatives like 'search_paper' or when not to use it (e.g., if only a count is needed).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FujishigeTemma/semantic-scholar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server