Skip to main content
Glama
Sign In
Paper Search MCP Server

Paper Search MCP Server

by h-lu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

read_crossref_paper

Provides guidance on alternative sources (arXiv, Sci-Hub, Semantic Scholar) for full-text access when given a CrossRef DOI, as CrossRef metadata does not include paper content.

Instructions

CrossRef does NOT support direct paper reading.

CrossRef provides metadata only, not full-text content.

INSTEAD (try in order):
1. read_arxiv_paper(id) - if arXiv preprint
2. read_scihub_paper(doi) - if published before 2023
3. read_semantic_paper(id) - last resort

Args:
    paper_id: DOI (e.g., '10.1038/nature12373').
    save_path: Unused.

Returns:
    Error message explaining alternatives.

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": "read_crossref_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idYes
save_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

Discloses that the tool returns an error message explaining alternatives, and notes that save_path is unused, providing full behavioral transparency despite no annotations.

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?

Front-loaded with key limitation, followed by structured alternatives list, parameter explanation, and return description. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, limitations, alternatives, parameters, and return behavior completely for a tool that returns an error. No output schema needed.

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?

Adds crucial meaning beyond schema: explains paper_id as DOI with example, and clarifies save_path is unused, compensating for 0% schema description coverage.

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?

Description explicitly states that the tool does not support direct paper reading, only metadata, which clearly distinguishes it from sibling tools like read_arxiv_paper and read_scihub_paper.

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

Usage Guidelines5/5

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

Provides explicit instructions for alternatives in a numbered list, telling the agent when not to use this tool and what to use instead.

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