Skip to main content
Glama
sid12super

MCP-Deep-Researcher

by sid12super

deep_researcher_research

Decomposes research questions into targeted sub-questions, searches the web in parallel, scores source credibility, and synthesizes a structured markdown report with findings and citations.

Instructions

Run a multi-agent research pipeline that decomposes a query into sub-questions, searches the web in parallel via Tavily, scores source credibility, and synthesizes a comprehensive markdown report with findings, knowledge gaps, and cited sources.

The pipeline has three stages:
  1. Planner — breaks the query into 3-5 targeted sub-questions (GPT-4o)
  2. Searcher — runs parallel Tavily web searches with credibility scoring
  3. Synthesizer — produces a structured markdown report (GPT-4o)

Results are cached for 24 hours. Identical (query + context + depth) combinations
return instantly on subsequent calls.

Args:
    params (ResearchInput): Validated input containing:
        - query (str): The research question (3-2000 chars)
        - search_depth (SearchDepth): 'basic' for speed or 'advanced' for depth
        - conversation_context (str): Prior research for multi-turn follow-ups

Returns:
    str: Markdown research report with executive summary, key findings per
         sub-question, knowledge gaps, and numbered source citations with
         credibility tags (high/medium/unverified).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes
Behavior5/5

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

No annotations provided, so the description bears full burden. It discloses the three-stage pipeline, 24-hour caching, parallel web search, credibility scoring, and structured output format. No contradictions or missing critical details.

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?

Description is well-structured: first sentence summarizes, then bullet points for stages, caching info, and parameter details. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description details the return format (markdown report with sections). It covers caching, parameters, and pipeline. Complete for a tool of this complexity.

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 low (0% per context signals, though properties have some description). The description adds significant value by explaining the search_depth options with time estimates and the purpose of conversation_context for multi-turn follow-ups, compensating for schema gaps.

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?

Description states explicitly: 'Run a multi-agent research pipeline that decomposes a query into sub-questions, searches the web...' and lists stages and output format. It is specific and distinct, even without sibling tools listed.

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

Usage Guidelines4/5

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

Clear that the tool is for complex research queries requiring decomposition, with caching noted. No explicit 'when not to use' or alternatives, but the context of no siblings makes this less critical.

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/sid12super/MCP-Deep-Researcher'

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