Skip to main content
Glama
openags

Paper Search MCP

by openags

search_openalex

Search academic papers from OpenAlex using a query to find relevant research publications and metadata.

Instructions

Search academic papers from OpenAlex.

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 tool 'search_openalex' is defined as an MCP tool using the @mcp.tool() decorator and implemented as an asynchronous function. It wraps a generic 'async_search' call using an 'openalex_searcher'.
    @mcp.tool()
    async def search_openalex(query: str, max_results: int = 10) -> List[Dict]:
        """Search academic papers from OpenAlex.
    
        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(openalex_searcher, query, max_results)
        return papers if papers else []
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') which is helpful, but doesn't disclose important behavioral traits like rate limits, authentication requirements, error conditions, pagination behavior, or whether this is a read-only operation. The description is minimal beyond basic functionality.

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?

Well-structured with clear sections (Args, Returns) and front-loaded purpose statement. Every sentence adds value, though the 'Returns' section could be slightly more detailed given the lack of output schema visibility in this context.

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 2 parameters with no schema descriptions, the description adequately covers parameter semantics. However, as a search tool with many alternatives and no annotations, it lacks context about OpenAlex's scope, limitations, or comparison to other search tools. The existence of an output schema helps, but the description doesn't leverage this to provide richer context.

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 string with an example, and 'max_results' with its default value. This adds meaningful semantics beyond the bare schema, though it doesn't cover parameter constraints or advanced query syntax.

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 searches academic papers from OpenAlex with a specific verb ('Search') and resource ('academic papers from OpenAlex'). It distinguishes from sibling tools by specifying the OpenAlex source, but doesn't explicitly differentiate from other search_* tools in the same domain.

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 on when to use this tool versus alternatives. With many sibling search tools (search_arxiv, search_pubmed, etc.), the description provides no context about when OpenAlex is preferable, what it specializes in, or when other search tools might be more appropriate.

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