Skip to main content
Glama
DaniManas
by DaniManas

find_research_gaps

Analyze academic papers to identify research gaps and unanswered questions in a specific topic, helping researchers discover future study directions.

Instructions

Analyze multiple papers on a topic to identify research gaps and unanswered questions.

Args: query: Research topic to analyze num_papers: Number of papers to analyze (default: 5, max: 10)

Returns: Analysis of research gaps, limitations, and future research directions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
num_papersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Main execution logic for the find_research_gaps tool: searches papers using PaperFetcher, fetches abstracts, and formats comprehensive instructions for LLM-based gap analysis.
    @mcp.tool()
    def find_research_gaps(query: str, num_papers: int = 5) -> str:
        """
        Analyze multiple papers on a topic to identify research gaps and unanswered questions.
    
        Args:
            query: Research topic to analyze
            num_papers: Number of papers to analyze (default: 5, max: 10)
    
        Returns:
            Analysis of research gaps, limitations, and future research directions
        """
        if num_papers > 10:
            num_papers = 10
    
        papers = fetcher.search_papers(query=query, max_results=num_papers, sort_by="cited_by_count")
    
        if papers and "error" in papers[0]:
            return papers[0]["error"]
    
        if not papers:
            return f"No papers found for query: {query}"
    
        result = f"**Research Gap Analysis for: '{query}'**\n"
        result += f"**Analyzing {len(papers)} highly-cited papers**\n\n"
    
        result += "**Papers Analyzed:**\n"
        paper_ids = []
        for i, paper in enumerate(papers, 1):
            result += f"{i}. {paper['title']} ({paper['publication_year']}) - {paper['cited_by_count']} citations\n"
            paper_ids.append(paper['id'])
    
        result += "\n**Fetching abstracts for deep analysis...**\n\n"
    
        abstracts_data = []
        for i, paper_id in enumerate(paper_ids, 1):
            paper_detail = fetcher.fetch_paper_by_id(paper_id)
            if "error" not in paper_detail:
                abstract_text = fetcher.get_paper_abstract(paper_detail)
                abstracts_data.append(f"**Paper {i}:** {paper_detail['title']}\n{abstract_text}\n")
    
        result += "".join(abstracts_data)
    
        result += "\n**Gap Analysis Instructions:**\n"
        result += "Based on the abstracts above, please identify:\n\n"
        result += "1. **Unanswered Research Questions:**\n"
        result += "   - What questions do these papers raise but not answer?\n"
        result += "   - What do the authors suggest for future research?\n\n"
        result += "2. **Methodological Limitations:**\n"
        result += "   - What limitations do the authors acknowledge?\n"
        result += "   - What methods or approaches are missing?\n\n"
        result += "3. **Understudied Areas:**\n"
        result += "   - What aspects of the topic receive less attention?\n"
        result += "   - What populations, contexts, or scenarios are not covered?\n\n"
        result += "4. **Contradictions & Inconsistencies:**\n"
        result += "   - Where do findings conflict?\n"
        result += "   - What requires further investigation to resolve?\n\n"
        result += "5. **Emerging Opportunities:**\n"
        result += "   - What new research directions are suggested?\n"
        result += "   - What interdisciplinary connections could be made?\n"
    
        return result
  • Type hints and docstring defining input parameters (query: str, num_papers: int=5) and output (str) for the tool.
    def find_research_gaps(query: str, num_papers: int = 5) -> str:
        """
        Analyze multiple papers on a topic to identify research gaps and unanswered questions.
    
        Args:
            query: Research topic to analyze
            num_papers: Number of papers to analyze (default: 5, max: 10)
    
        Returns:
            Analysis of research gaps, limitations, and future research directions
        """
  • src/server.py:209-209 (registration)
    Decorator that registers the find_research_gaps function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions analyzing 'multiple papers' and default/max values for 'num_papers', but lacks critical details: whether this requires external API calls, potential rate limits, processing time, or how papers are sourced (e.g., from a database vs. web search). For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 well-structured with a purpose statement, parameter details, and return value explanation in separate sections. It's appropriately sized—each sentence adds value without redundancy. Minor improvement could be front-loading the return details more clearly, but overall it's efficient.

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 0% schema coverage and no annotations, the description does a fair job explaining parameters and returns. However, the output schema exists ('Returns: Analysis of research gaps...'), so description needn't detail return values. The main gap is lack of behavioral context (e.g., how papers are retrieved), making it incomplete for a tool that likely involves complex operations.

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 provides clear semantics for both parameters: 'query' as the 'Research topic to analyze' and 'num_papers' as 'Number of papers to analyze' with default and max values. This adds meaningful context beyond the bare schema types, though it doesn't specify format expectations for 'query' (e.g., keywords vs. natural language).

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's purpose: 'Analyze multiple papers on a topic to identify research gaps and unanswered questions.' It specifies the verb ('analyze'), resource ('multiple papers'), and outcome ('identify research gaps'). However, it doesn't explicitly differentiate from siblings like 'compare_papers' or 'extract_claims' beyond the gap-finding focus.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for gap analysis in research topics, but provides no explicit guidance on when to use this tool versus alternatives like 'search_papers' or 'compare_papers'. The context of analyzing 'multiple papers' suggests it's for synthesis rather than single-paper operations, but this is only implied, not stated as a guideline.

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/DaniManas/ResearchMCP'

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