Web Search & Data API

related_papers

Literature review and related-paper discovery. Given a seed paper (arXiv id, DOI, or OpenAlex id) or a topic query, returns semantically similar and recommended scholarly papers to expand a reading list or systematic review, via Semantic Scholar recommendations with an OpenAlex related-works fallback. Keyless. [$0.03/call]. Params — id: paper arXiv id, DOI, or OpenAlex id; doi: alias for id (DOI form); q: query (alternative to id — relevance search); maxItems: 1-50 Example params: {'doi': '10.48550/arXiv.1706.03762', 'maxItems': 10}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "related_papers"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses keyless access and cost ($0.03/call) and mentions the fallback mechanism ('via Semantic Scholar recommendations with an OpenAlex related-works fallback'). It does not mention rate limits or error handling, but these are not critical for a read-only search tool.

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?

The description is well-structured: purpose, input type, service details, cost, parameter list, and example. It is slightly long but each sentence adds value. The example clarifies usage without redundant text.

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?

There is no output schema, so the description should give some output context. It states the tool 'returns semantically similar and recommended scholarly papers', which is a high-level output, but does not detail response structure or error behaviors. For this simple search tool, the omission is minor and does not hinder basic use.

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?

Although the JSON schema only wraps a generic 'params' object, the description thoroughly explains each parameter: id (arXiv/DOI/OpenAlex), doi (alias for DOI), q (query alternative), and maxItems (1-50). It also provides an example usage. This fully compensates for the schema's lack of detail.

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: 'Literature review and related-paper discovery' that returns 'semantically similar and recommended scholarly papers' given a seed paper or topic query. It names the specific resources (Semantic Scholar with OpenAlex fallback) and distinguishes itself from sibling tools like author_search or paper_details by focusing on related-paper discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear conditions for use: 'Given a seed paper (arXiv id, DOI, or OpenAlex id) or a topic query'. It also suggests a use case: 'to expand a reading list or systematic review'. However, it does not explicitly compare to sibling tools or state when not to use it, leaving some inference to the agent.

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

All Web Search & Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?