Skip to main content
Glama
openags

Paper Search MCP

by openags

search_zenodo

Search academic papers from Zenodo open repository using query terms to find relevant research publications.

Instructions

Search academic papers from Zenodo open repository.

Args: query: Search query string (e.g., 'machine learning'). max_results: Maximum number of papers to return (default: 10). Returns: List of paper metadata in dictionary format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `search_zenodo` tool implementation, which serves as the MCP tool handler and orchestrates the search using the `ZenodoSearcher` class.
    async def search_zenodo(query: str, max_results: int = 10) -> List[Dict]:
        """Search academic papers from Zenodo open repository.
    
        Args:
            query: Search query string (e.g., 'machine learning').
            max_results: Maximum number of papers to return (default: 10).
        Returns:
            List of paper metadata in dictionary format.
        """
        papers = await async_search(zenodo_searcher, query, max_results)
        return papers if papers else []
  • The `ZenodoSearcher.search` method, which interacts with the Zenodo public REST API to perform the search operation.
    def search(self, query: str, max_results: int = 10, **kwargs) -> List[Paper]:
        """Search Zenodo records.
    
        Args:
            query: Free-text or Elasticsearch query string.
            max_results: Maximum number of results (1–200; Zenodo page limit is 10k).
            **kwargs: Extra filters:
                - ``type``: Record type, e.g. ``"publication"`` (default), ``"dataset"``,
                  ``"image"``, ``"video"``, ``"software"``, ``"poster"``, etc.
                - ``subtype``: Publication subtype, e.g. ``"article"``, ``"preprint"``.
                - ``year``: Filter by publication year (e.g. ``2023``).
                - ``access_right``: ``"open"``, ``"embargoed"``, ``"restricted"``, ``"closed"``.
    
        Returns:
            List of :class:`~paper_search_mcp.paper.Paper` objects.
        """
        max_results = max(1, min(max_results, 200))
    
        params: Dict[str, Any] = {
            "q": query,
            "size": max_results,
            "sort": "mostrecent",
        }
    
        record_type = kwargs.get("type", "publication")
        if record_type:
            params["type"] = record_type
    
        subtype = kwargs.get("subtype", "")
        if subtype:
            params["subtype"] = subtype
    
        access_right = kwargs.get("access_right", "")
        if access_right:
            params["access_right"] = access_right
    
        year = kwargs.get("year")
        if year:
            params["q"] = f"{query} AND publication_date:[{year}-01-01 TO {year}-12-31]"
    
        try:
            response = self.session.get(
                f"{self.BASE_URL}/records", params=params, timeout=20
            )
            response.raise_for_status()
            data = response.json()
        except Exception as exc:
            logger.error("Zenodo search failed: %s", exc)
            return []
    
        papers: List[Paper] = []
        for hit in data.get("hits", {}).get("hits", []):
            paper = self._parse_record(hit)
            if paper:
                papers.append(paper)
    
        return papers
  • Registration of the Zenodo search functionality within the task mapping in the server.
    task_map[source] = search_zenodo(query, max_results_per_source)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the return format ('List of paper metadata in dictionary format') but lacks critical behavioral details like rate limits, authentication requirements, pagination behavior, error conditions, or whether this is a read-only operation. For a search tool with no annotation coverage, this is insufficient.

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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value, though the 'Returns' section could be slightly more specific about what metadata fields are included.

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 moderate complexity (2 parameters), no annotations, but with an output schema present, the description is minimally adequate. It covers the basic purpose and parameters but lacks behavioral context and usage guidance. The output schema existence means the description doesn't need to detail return values, but other gaps remain.

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?

With 0% schema description coverage, the description compensates well by explaining both parameters: 'query' as a search query string with an example, and 'max_results' with its default value. This adds meaningful context beyond the bare schema, though it doesn't cover advanced query syntax or result limits.

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 searches academic papers from the Zenodo open repository, specifying both the action ('search') and resource ('academic papers'). It distinguishes itself from sibling tools like 'download_zenodo' and 'read_zenodo_paper' by focusing on search functionality rather than download or read operations.

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 search tools (e.g., search_arxiv, search_pubmed), there's no indication of when Zenodo-specific searching is appropriate or what differentiates it from other academic search tools.

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