Skip to main content
Glama
enesjakozh
openags

Paper Search MCP

by openags
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

download_dblp

Check PDF availability for dblp papers and receive guidance on alternative access methods when direct download is not supported.

Instructions

Download PDF for a paper from dblp.

Note: dblp doesn't provide direct PDF access. This function returns an informative message.

Args: paper_id: dblp paper identifier. save_path: Directory to save the PDF (default: './downloads'). Returns: str: Message indicating that direct PDF download is not supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • paper_search_mcp/server.py:1066-1078 (handler)
    The download_dblp handler in server.py calls the DBLPSearcher.download_pdf method.
    async def download_dblp(paper_id: str, save_path: str = "./downloads") -> str:
    """Download PDF for a paper from dblp.

    Note: dblp doesn't provide direct PDF access.
    This function returns an informative message.

    Args:
        paper_id: dblp paper identifier.
        save_path: Directory to save the PDF (default: './downloads').
    Returns:
        str: Message indicating that direct PDF download is not supported.
    """
    return dblp_searcher.download_pdf(paper_id, save_path)
  • paper_search_mcp/academic_platforms/dblp.py:324-344 (handler)
    The DBLPSearcher.download_pdf method, which is invoked by the download_dblp handler, raises a NotImplementedError as dblp does not support direct PDF downloads.
    def download_pdf(self, paper_id: str, save_path: str) -> str:
    """
    Download PDF for a dblp paper.

    Note: dblp doesn't provide direct PDF access.
    This method tries to find PDF through DOI or other sources.

    Args:
        paper_id: dblp paper identifier
        save_path: Directory to save the PDF

    Returns:
        Path to the saved PDF file

    Raises:
        NotImplementedError: dblp doesn't support direct PDF downloads
    """
    raise NotImplementedError(
        "dblp doesn't provide direct PDF access. "
        "Use DOI to download from other sources (Crossref, publisher sites, etc.)."
    )

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it doesn't actually download a PDF (due to dblp's limitations) and returns an informative message instead. This transparency helps the agent understand the tool's actual behavior, though it could add more context like error handling or rate limits.

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?

The description is well-structured and concise: a clear purpose statement, a note on limitations, and brief parameter and return explanations. Every sentence adds value without redundancy, making it easy for an agent to parse quickly.

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?

Given the tool's low complexity (2 parameters, no annotations, but with an output schema), the description is complete. It covers purpose, limitations, parameters, and return value, and the output schema handles return details, so no gaps remain for effective agent use.

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 both parameters: 'paper_id: dblp paper identifier' and 'save_path: Directory to save the PDF (default: './downloads').' This adds meaning beyond the schema's basic types, clarifying what each parameter represents and the default value for save_path.

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: 'Download PDF for a paper from dblp.' It specifies the verb ('Download'), resource ('PDF for a paper'), and source ('from dblp'), distinguishing it from sibling tools like 'read_dblp_paper' or other download tools for different sources.

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 provides explicit usage guidance: 'Note: dblp doesn't provide direct PDF access. This function returns an informative message.' This tells the agent when to use it (for dblp papers) and when not to expect a PDF download, setting clear expectations compared to alternatives like 'download_arxiv' or 'download_scihub'.

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