Skip to main content
Glama
openags

Paper Search MCP

by openags

search_google_scholar

Search academic papers from Google Scholar to find relevant research publications using specific queries and return paper metadata.

Instructions

Search academic papers from Google Scholar.

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 MCP tool handler `search_google_scholar` which calls the `async_search` helper.
    async def search_google_scholar(query: str, max_results: int = 10) -> List[Dict]:
        """Search academic papers from Google Scholar.
    
        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(google_scholar_searcher, query, max_results)
        return papers if papers else []
  • The implementation of the search logic for Google Scholar within the `GoogleScholarSearcher` class.
    def search(self, query: str, max_results: int = 10) -> List[Paper]:
        """
        Search Google Scholar with custom parameters
        """
        papers = []
        start = 0
        results_per_page = min(10, max_results)
    
        while len(papers) < max_results:
            try:
                # Construct search parameters
                params = {
                    'q': query,
                    'start': start,
                    'hl': 'en',
                    'as_sdt': '0,5'  # Include articles and citations
                }
    
                response = None
                for attempt in range(self.max_retries):
                    self._rotate_user_agent()
                    time.sleep(random.uniform(1.0, 2.5))
    
                    response = self.session.get(self.SCHOLAR_URL, params=params, timeout=30)
                    if response.status_code == 200:
                        break
    
                    if response.status_code in (403, 429, 503):
                        wait_time = self.retry_delay * (2 ** attempt)
                        wait_time += random.uniform(0, 0.5)
                        logger.warning(
                            "Google Scholar returned %s (attempt %s/%s). Backing off %.1fs",
                            response.status_code,
                            attempt + 1,
                            self.max_retries,
                            wait_time,
                        )
                        time.sleep(wait_time)
                        continue
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 offers minimal behavioral insight. It mentions the return format ('List of paper metadata in dictionary format'), which adds some value, but lacks details on rate limits, authentication needs, result ordering, or error handling. For a search tool with no annotations, this is inadequate.

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 well-structured and front-loaded with the core purpose, followed by Args and Returns sections. Every sentence earns its place by providing essential information without redundancy, making it efficient and easy to parse.

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 (search with 2 parameters), no annotations, and an output schema (implied by 'Returns'), the description is partially complete. It covers parameters well but lacks behavioral context and usage guidelines. The output schema reduces the need to detail return values, but overall completeness is limited.

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 effectively explains both parameters: 'query' as a search string with an example, and 'max_results' with its default value. This adds clear meaning beyond the bare schema, though it doesn't cover constraints like query length or max_results range.

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 Google Scholar, which is a specific verb ('search') and resource ('academic papers from Google Scholar'). It distinguishes from sibling tools like 'search_arxiv' or 'search_pubmed' by specifying the Google Scholar source, though it doesn't explicitly contrast them.

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 the many sibling search tools (e.g., search_arxiv, search_pubmed, search_crossref). The description lacks context about Google Scholar's coverage, strengths, or limitations compared to alternatives, leaving the agent without usage direction.

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