OpenPapers

Get related papers

get_related_papers

Find related papers for a paper ID using Semantic Scholar recommendations with provenance, preserving evidence for reproducible research workflows.

Instructions

Retrieve Semantic Scholar recommendations with provenance.

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_related_papers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`paper_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 2, 2026

TDQS

C2.2/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. 'Retrieve' implies a read operation, but the description does not disclose any behavioral details such as response format, pagination, rate limits, error behavior, or what 'provenance' means in practice.

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

Conciseness3/5

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

The description is brief and to the point, with no wasted words. However, the brevity borders on under-specification, and the phrase 'with provenance' is unexplained, so the structure is not as effective as it could be.

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?

For a tool with no annotations, no output schema, and a 0% parameter description coverage, this description is too thin to let an agent correctly invoke the tool. It lacks parameter semantics, expected output, and relationship to sibling tools.

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

Parameters1/5

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

Schema description coverage is 0%, and the description says nothing about paper_id or limit. The schema provides only type/default/min/max constraints, leaving the agent without any explanation of what each parameter means or how they affect the request.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific action and resource: 'Retrieve Semantic Scholar recommendations with provenance.' This is more specific than a mere restatement, but it does not distinguish the tool from related sibling tools like get_references or get_citations, and 'provenance' is vague.

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 guidance is given about when to use this tool versus alternatives. With 35 sibling tools including several retrieval-related options, the absence of any selection criteria leaves the agent to infer the appropriate use case.

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