Skip to main content
Glama
jerpint

paperpal

by jerpint

fetch_paper_details_from_arxiv

Retrieve paper details from arXiv using IDs to access metadata, abstracts, and publication information for research analysis.

Instructions

Get the Arxiv info for a list of papers.

Args:
    arxiv_ids (list[str] | str): The IDs of the papers to get the Arxiv info for, e.g. ["2503.01469", "2503.01470"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
arxiv_idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool() registers and implements the 'fetch_paper_details_from_arxiv' tool. It accepts arxiv_ids (str or list[str]), fetches paper details asynchronously from Arxiv via get_arxiv_info_from_arxiv_ids, formats them using stringify_papers, and returns a string representation.
    @mcp.tool()
    async def fetch_paper_details_from_arxiv(arxiv_ids: list[str] | str) -> str:
        """Get the Arxiv info for a list of papers.
    
        Args:
            arxiv_ids (list[str] | str): The IDs of the papers to get the Arxiv info for, e.g. ["2503.01469", "2503.01470"]
        """
        arxiv_papers: list[ArxivPaper] = await get_arxiv_info_from_arxiv_ids(arxiv_ids)
        return stringify_papers(arxiv_papers)
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 of behavioral disclosure. It states the tool fetches info but doesn't describe key behaviors like whether it's a read-only operation, error handling for invalid IDs, rate limits, or authentication needs. This is a significant gap for a tool with no annotation coverage.

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 appropriately sized and front-loaded, with the main purpose stated first and parameter details following. It uses two sentences efficiently, with no wasted words, making it easy to parse quickly.

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 the tool's low complexity (1 parameter) and the presence of an output schema, the description is somewhat complete but has gaps. It covers the basic purpose and parameter usage but lacks behavioral details and usage guidelines. With an output schema, it doesn't need to explain return values, but overall it's only minimally adequate.

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?

The description adds meaningful semantics beyond the input schema. The schema has 0% description coverage, but the description explains that 'arxiv_ids' can be a list or string and provides an example (e.g., ["2503.01469", "2503.01470"]), clarifying usage. With only one parameter, this compensates well for the low schema coverage.

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: 'Get the Arxiv info for a list of papers.' It specifies the verb ('Get') and resource ('Arxiv info'), making it understandable. However, it doesn't explicitly differentiate from the sibling tool 'semantic_search_papers_on_huggingface', which appears to be a search tool rather than a direct fetch by ID, so it misses full sibling distinction.

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. It doesn't mention the sibling tool or any other context for usage, such as prerequisites or scenarios where this tool is preferred over others. This leaves the agent without explicit direction on tool selection.

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/jerpint/paperpal'

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