Skip to main content
Glama
Sign In
semanticscholar-mcp

semanticscholar-mcp

by xbghc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Paper References

get_paper_references

Retrieve the reference list of a scholarly paper using its paper ID. Get cited works with pagination and limit options for efficient analysis.

Instructions

获取论文的参考文献列表（这篇论文引用了什么）

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": {
      "paperId": "<paperId>"
    },
    "name": "get_paper_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回数量，最大 1000
offsetNo分页偏移量
paperIdYes论文 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
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 of behavioral disclosure. It only states the core action and does not mention pagination behavior, return format, rate limits, or potential errors. As a read operation, side effects are minimal, but the agent has no information about response structure or operational nuances.

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 with no filler. It efficiently conveys the purpose without unnecessary words.

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?

There is no output schema and no annotations, yet the description does not explain the return values or pagination details. While the schema documents parameters, the agent has no insight into what the reference list contains (e.g., titles, authors) or how to handle paging. This leaves significant gaps for a tool that could return potentially large lists.

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?

All three parameters (paperId, limit, offset) have exhaustive descriptions in the input schema, providing 100% coverage. The tool description adds no additional parameter semantics beyond what the schema already offers, so a baseline score of 3 is appropriate.

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 uses a specific verb (获取/get) and clearly identifies the resource as the paper's reference list, explicitly clarifying that these are works cited by the paper. This distinguishes it from the sibling tool get_paper_citations, which would retrieve works citing the paper.

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?

No explicit guidance is provided on when to use this tool versus alternatives like get_paper_citations or get_paper. The differentiation is only implicit through the wording of the description, not directly stated.

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

Deploy Server

Other Tools