Skip to main content
Glama
openags

Paper Search MCP

by openags

read_biorxiv_paper

Extract text content from bioRxiv paper PDFs using DOI identifiers to access and analyze scientific research documents.

Instructions

Read and extract text content from a bioRxiv paper PDF.

Args: paper_id: bioRxiv DOI. save_path: Directory where the PDF is/will be saved (default: './downloads'). Returns: str: The extracted text content of the paper.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of read_paper which downloads and extracts text from a bioRxiv PDF.
    def read_paper(self, paper_id: str, save_path: str = "./downloads") -> str:
        """
        Read a paper and convert it to text format.
        
        Args:
            paper_id: bioRxiv DOI
            save_path: Directory where the PDF is/will be saved
            
        Returns:
            str: The extracted text content of the paper
        """
        pdf_path = f"{save_path}/{paper_id.replace('/', '_')}.pdf"
        if not os.path.exists(pdf_path):
            pdf_path = self.download_pdf(paper_id, save_path)
        
        try:
            reader = PdfReader(pdf_path)
            text = ""
            for page in reader.pages:
                text += page.extract_text() + "\n"
            return text.strip()
        except Exception as e:
            print(f"Error reading PDF for paper {paper_id}: {e}")
            return ""
  • The MCP server wrapper for the read_biorxiv_paper tool that calls the BioRxivSearcher implementation.
    async def read_biorxiv_paper(paper_id: str, save_path: str = "./downloads") -> str:
        """Read and extract text content from a bioRxiv paper PDF.
    
        Args:
            paper_id: bioRxiv DOI.
            save_path: Directory where the PDF is/will be saved (default: './downloads').
        Returns:
            str: The extracted text content of the paper.
        """
        try:
            return biorxiv_searcher.read_paper(paper_id, save_path)
        except Exception as e:
            print(f"Error reading paper {paper_id}: {e}")
            return ""
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. It mentions downloading and saving PDFs ('where the PDF is/will be saved'), implying network and file system operations, but doesn't disclose critical behaviors like error handling, rate limits, authentication needs, or whether it overwrites existing files. For a tool with potential side effects, this is inadequate.

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 and front-loaded with the core purpose, followed by parameter and return details. It uses minimal sentences efficiently, though the 'Args:' and 'Returns:' sections could be integrated more smoothly. There's little waste, but minor improvements in flow could enhance clarity.

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

Completeness3/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, and an output schema (which handles return values), the description is moderately complete. It covers the basic operation and parameters but lacks behavioral details (e.g., errors, side effects) and sibling differentiation. For a tool with potential downloads and file writes, more context is needed to be fully helpful.

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

Parameters3/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 adds meaning by explaining 'paper_id' as a 'bioRxiv DOI' and 'save_path' as a 'Directory where the PDF is/will be saved', which clarifies beyond schema titles. However, it doesn't cover format details (e.g., DOI structure, path requirements), leaving gaps. Baseline 3 is appropriate as it adds some value but not fully.

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

Purpose4/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: 'Read and extract text content from a bioRxiv paper PDF.' It specifies the verb ('read and extract'), resource ('bioRxiv paper PDF'), and output ('text content'). However, it doesn't explicitly differentiate from sibling tools like 'read_arxiv_paper' or 'download_biorxiv' beyond the bioRxiv focus, leaving some ambiguity about when to choose this over similar tools.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools for different sources (e.g., 'read_arxiv_paper', 'download_biorxiv'), there's no indication of whether this tool downloads, reads, or both, or how it compares to other bioRxiv-related tools. Usage is implied only by the tool name and description focus.

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