Skip to main content
Glama
wr-web
by wr-web

list_papers

Retrieve available arXiv papers to search, download, or read scientific research through the MCP interface.

Instructions

List all existing papers available as resources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main asynchronous handler function that executes the list_papers tool: lists local papers, fetches metadata from arXiv API, formats as JSON.
    async def handle_list_papers(
        arguments: Optional[Dict[str, Any]] = None,
    ) -> List[types.TextContent]:
        """Handle requests to list all stored papers."""
        try:
            papers = list_papers()
    
            client = arxiv.Client()
    
            results = client.results(arxiv.Search(id_list=papers))
    
            response_data = {
                "total_papers": len(papers),
                "papers": [
                    {
                        "title": result.title,
                        "summary": result.summary,
                        "authors": [author.name for author in result.authors],
                        "links": [link.href for link in result.links],
                        "pdf_url": result.pdf_url,
                    }
                    for result in results
                ],
            }
    
            return [
                types.TextContent(type="text", text=json.dumps(response_data, indent=2))
            ]
    
        except Exception as e:
            return [types.TextContent(type="text", text=f"Error: {str(e)}")]
  • Defines the MCP Tool object for list_papers, including name, description, and empty input schema (no parameters required).
    list_tool = types.Tool(
        name="list_papers",
        description="List all existing papers available as resources",
        inputSchema={
            "type": "object",
            "properties": {},
            "required": [],
        },
    )
  • Registers the list_papers tool schema (via 'list_tool') with the MCP server by including it in the response to list_tools().
    @server.list_tools()
    async def list_tools() -> List[types.Tool]:
        """List available arXiv research tools."""
        return [search_tool, download_tool, list_tool, read_tool]
  • Maps tool name 'list_papers' to its handler function in the server's call_tool dispatcher.
    elif name == "list_papers":
        return await handle_list_papers(arguments)
  • Helper function that scans the storage directory for downloaded paper markdown files and returns their IDs.
    def list_papers() -> list[str]:
        """List all stored paper IDs."""
        return [p.stem for p in Path(settings.STORAGE_PATH).glob("*.md")]
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits such as pagination, rate limits, or what 'available as resources' entails. It's minimal and leaves key operational details unclear.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'papers' are, how they're listed, or the return format, leaving significant gaps for a tool that likely returns a list of resources.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is acceptable here, but it doesn't compensate for any gaps since there are none.

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 verb ('List') and resource ('all existing papers'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'search_papers' or 'read_paper', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives like 'search_papers' or 'download_paper'. The description implies a broad listing without filtering, but it lacks explicit instructions or exclusions.

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/wr-web/APR'

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