Skip to main content
Glama
Sign In
Paper Search MCP

Paper Search MCP

by openags
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

download_crossref

Download academic papers using CrossRef DOIs by accessing publisher websites, as CrossRef is a citation database without direct PDF downloads.

Instructions

Attempt to download PDF of a CrossRef paper.

Args: paper_id: CrossRef DOI (e.g., '10.1038/nature12373'). save_path: Directory to save the PDF (default: './downloads'). Returns: str: Message indicating that direct PDF download is not supported.

Note: CrossRef is a citation database and doesn't provide direct PDF downloads. Use the DOI to access the paper through the publisher's website.

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

Input Schema

NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.4/5.0
Behavior5/5

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

It transparently states that the tool always returns a failure message because CrossRef does not support PDF downloads, fully disclosing the tool's behavior beyond any annotations.

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 concise with clear Args/Returns/Note sections, though it could be slightly shorter without losing clarity.

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?

Given the tool's simple behavior (always fails), the description is complete, covering purpose, parameters, return value, and context. Adequate for a limited-function tool.

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?

The description explains paper_id as a CrossRef DOI with an example, and save_path as a directory with default, adding meaning beyond the bare schema.

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 that the tool attempts to download a PDF from CrossRef but returns a message indicating it is not supported. This is specific and distinguishes it from other download tools that may succeed.

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 description suggests using the DOI to access the paper through the publisher's website as an alternative, but it does not explicitly compare to sibling tools like download_scihub or provide when-to-use guidance.

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