Skip to main content
Glama
Sign In
semanticscholar-mcp

semanticscholar-mcp

by xbghc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Batch Get Papers

batch_get_papers

Retrieve detailed information for up to 500 papers at once by providing their paper IDs. Optionally specify fields to include only the data you need.

Instructions

批量获取多篇论文的详细信息（最多 500 篇）

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": {
      "paperIds": "<paperIds>"
    },
    "name": "batch_get_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo返回字段
paperIdsYes论文 ID 列表，最多 500 个

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/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, but it only states the batch size limit (which is already present in the schema's maxItems). It does not mention return format, what happens when invalid IDs are passed, ordering, pagination, or any error/edge-case behavior. This is a significant gap for a tool with no structured safety hints.

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

Conciseness4/5

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

A single, front-loaded sentence effectively communicates the core purpose. No filler or redundancy. It is appropriately concise, though it lacks any additional structured details that might naturally be included (e.g., noting the optional 'fields' parameter).

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?

The tool has only two parameters but no annotations and no output schema. The description only says 'detailed information', leaving unclear what the response shape is, how the 'fields' parameter affects results, and how failures are handled. This is incomplete for an agent aiming to invoke it correctly without additional context.

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% (both 'paperIds' and 'fields' have descriptions). The description adds no new meaning beyond restating the limit already captured by maxItems. Baseline 3 is appropriate because the schema carries the parameter semantics.

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 ('批量获取' / batch get) plus resource ('论文' / papers) and explicitly scopes it with a maximum of 500. It clearly distinguishes itself from the sibling 'get_paper' (single paper retrieval) and 'search_papers'.

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 intent is implied: use this when fetching multiple paper details at once. However, there is no explicit statement about when to use it over alternatives, nor any exclusions or prerequisites. It provides clear context but no direct comparison to 'get_paper' or other siblings.

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