Skip to main content
Glama
openags

Paper Search MCP

by openags

search_doaj

Search academic papers from DOAJ (Directory of Open Access Journals) using keywords to find relevant research articles.

Instructions

Search academic papers from DOAJ (Directory of Open Access Journals).

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 handler function for the 'search_doaj' tool, which uses an async_search helper with a doaj_searcher.
    async def search_doaj(query: str, max_results: int = 10) -> List[Dict]:
        """Search academic papers from DOAJ (Directory of Open Access Journals).
    
        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(doaj_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 the full burden. It mentions the tool returns a list of paper metadata but doesn't disclose behavioral traits such as rate limits, authentication needs, error handling, or pagination details. The description is minimal and lacks critical operational context.

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, starting with the core purpose followed by parameter details in a structured format. Every sentence adds value, though it could be slightly more concise by integrating the parameter explanations more seamlessly.

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 has an output schema), the description is somewhat complete but lacks depth. It covers the purpose and parameters but misses behavioral transparency and usage guidelines. The output schema existence means return values are documented elsewhere, reducing the burden, but overall completeness is adequate with clear gaps.

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 adds meaning by explaining that 'query' is a search query string with an example ('machine learning') and 'max_results' specifies the maximum number of papers with a default value. This clarifies parameter usage beyond the bare schema, though it could provide more detail on query syntax or constraints.

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 specific action ('Search academic papers') and resource ('from DOAJ'), distinguishing it from sibling tools like 'download_doaj' or 'read_doaj_paper' by focusing on search functionality rather than download or reading 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?

No explicit guidance on when to use this tool versus alternatives is provided. While the description mentions DOAJ as the source, it doesn't clarify when to prefer DOAJ over other search tools like 'search_arxiv' or 'search_pubmed' in the sibling list, nor does it mention prerequisites 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/openags/paper-search-mcp'

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