Skip to main content
Glama
enesjakozh
openags

Paper Search MCP

by openags
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

read_crossref_paper

Extract text content from academic papers using CrossRef DOIs. Note: CrossRef provides citation data; access full papers through publisher websites.

Instructions

Attempt to read and extract text content from a CrossRef paper.

Args: paper_id: CrossRef DOI (e.g., '10.1038/nature12373'). save_path: Directory where the PDF is/will be saved (default: './downloads'). Returns: str: Message indicating that direct paper reading is not supported.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • paper_search_mcp/server.py:846-859 (handler)
    The MCP tool handler in server.py which delegates the reading request to the crossref_searcher instance.
    async def read_crossref_paper(paper_id: str, save_path: str = "./downloads") -> str:
    """Attempt to read and extract text content from a CrossRef paper.

    Args:
        paper_id: CrossRef DOI (e.g., '10.1038/nature12373').
        save_path: Directory where the PDF is/will be saved (default: './downloads').
    Returns:
        str: Message indicating that direct paper reading is not supported.
        
    Note:
        CrossRef is a citation database and doesn't provide direct paper content.
        Use the DOI to access the paper through the publisher's website.
    """
    return crossref_searcher.read_paper(paper_id, save_path)
  • paper_search_mcp/academic_platforms/crossref.py:249-264 (handler)
    The implementation of read_paper in the CrossRefSearcher class, which explicitly returns an informative message that reading is not supported.
    def read_paper(self, paper_id: str, save_path: str = "./downloads") -> str:
    """
    CrossRef doesn't provide direct paper content access.
    
    Args:
        paper_id: DOI of the paper
        save_path: Directory for potential PDF storage (unused)
        
    Returns:
        str: Error message indicating PDF reading is not supported
    """
    message = ("CrossRef papers cannot be read directly through this tool. "
              "CrossRef is a citation database that provides metadata about academic papers. "
              "Only metadata and abstracts are available through CrossRef's API. "
              "To access the full text, please use the paper's DOI or URL to visit the publisher's website.")
    return message

Tool Definition Quality

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the tool only 'attempts' to read (implying potential failure), it saves PDFs to a directory, and it returns a message indicating lack of support rather than actual content. This adds valuable context beyond basic functionality.

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 with sections for Args, Returns, and Note, making it easy to parse. It's front-loaded with the main purpose. Some redundancy exists (e.g., repeating the limitation in Note and Returns), but overall it's efficient with minimal waste.

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 no annotations, 0% schema coverage, but an output schema exists, the description is reasonably complete. It covers purpose, parameters, return behavior, and critical limitations. However, it could better explain the 'attempt' process or error handling for a tool with inherent constraints.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It explains 'paper_id' as a 'CrossRef DOI' with an example, and 'save_path' as a directory for PDF saving with a default. This adds meaningful semantics beyond the bare schema, though it could detail format constraints more.

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 states 'Attempt to read and extract text content from a CrossRef paper,' which provides a clear verb ('read and extract') and resource ('CrossRef paper'). However, it doesn't differentiate from siblings like 'read_arxiv_paper' beyond the source, and the purpose is somewhat vague due to the 'attempt' qualifier and later note about limitations.

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?

The description explicitly states when not to use this tool: 'CrossRef is a citation database and doesn't provide direct paper content. Use the DOI to access the paper through the publisher's website.' This provides clear alternatives and exclusions, helping the agent avoid misuse.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openags/paper-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server