Skip to main content
Glama
605,263 tools. Updated 2026-09-23 23:31

"Deep Research on MCP (Master Control Program or Related Topic)" matching MCP tools:

  • Perform comprehensive research on a topic. Decomposes your query into sub-queries, searches and reads multiple sources in parallel, then synthesizes a structured report with citations. Best for open-ended or comparative questions that need coverage from many angles. For simple factual lookups, use search instead (optionally with include_answer=true for cheap synthesis). Costs 50 credits. Returns: query, report (structured markdown with citations), sources (array of {title, url, fetched}), sub_queries (the decomposed queries), credits_used, credits_remaining, usage (token counts). Args: query: The research question or topic topic: "general" (default) or "news" (prioritize recent news articles) freshness: Filter by recency - "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD" max_sources: Maximum number of sources to use, 5-30 (default 20)
    ConnectorNo auth
  • Retrieve reference documentation for the Zaira Guide API and MCP server on demand. Topics: - getting_started — how to connect via MCP or REST, first queries - endpoints — full REST endpoint reference with parameters - mcp_tools — MCP tool reference with when-to-use guidance and a routing matrix - schema — the tool entry schema - errors — error taxonomy for REST (RFC 9457) and MCP (JSON-RPC) Call with no topic to get an index of available topics. Returns: the requested topic as a Markdown-KV block. With no topic, returns an index listing all available topics with short descriptions; call again with the relevant topic for the full content. Examples (topic selection): - "How do I call the REST API?" → {topic: "getting_started"} - "What parameters does /tools accept?" → {topic: "endpoints"} - "What fields are in a tool entry?" → {topic: "schema"} - "What error shapes do I handle, and what are the recovery steps?" → {topic: "errors"} - "Which MCP tool fits my task?" → {topic: "mcp_tools"} Edge cases: - No topic argument is valid — you get the index. This is the deferred-loading path; don't load every topic at once. - Topic must match the enum exactly (lowercase, underscore). "getting-started" with a hyphen is rejected as an unknown parameter. Risk: read-only, closed-world, idempotent — no state change possible.
    ConnectorNo auth
  • Search the user's files by filename and return matching documents in the deep-research result shape. ALIAS: this is the SAME search as search_files (same data, same permissions) - use it when your client requires the id/title/url search contract (ChatGPT deep research); otherwise prefer search_files for richer file metadata. Each result's id can be passed to fetch (or get_file) to read that document. Read-only; nothing is written, so it is safe to call.
    ConnectorNo auth
  • List the shows most related to a podcast, best first — "shows like this show". Each result carries the related show's slug, a calibrated score in (0,1], and a coarse band (strong: same beat and audience; moderate: overlapping subject or audience; weak: a loose connection) to branch on. Add `include: ["basis"]` to see WHY each pair is related: content similarity of recent episodes, shared topics, shared guests (named), same publisher, shared sponsors — use it to explain a recommendation or to keep only pairs related for the reason you care about (shared guests for booking, content for media planning). Related sets are precomputed per show from its transcripts, topic profile, guest roster, network and advertisers, restricted to the show's language. Only shows above a relatedness floor are listed, machine-generated and farmed feeds are never listed, and a publisher's duplicate feeds of one show appear once. An empty FIRST page is not an error: its `coverage` says whether the set is not computed yet, nothing cleared the floor, or the request's filters and the default policy removed everything; an empty page reached through a cursor is simply the end of the list. Not a topic browser: for shows that COVER a topic use `particle_podcast_resolve` with `topic_slug`. Not a guest lookup: for where a person has appeared use `particle_podcast_get_guest`. Not advertiser co-occurrence: use `particle_podcast_get_sponsors`. Every related show's slug feeds `particle_podcast_resolve`, `particle_podcast_list_episodes` and the other podcast tools; person slugs in the basis feed `particle_podcast_get_guest`, topic slugs feed `particle_podcast_resolve`'s `topic_slug`. For the five most related shows inline on a resolve, pass `include: ["related"]` to `particle_podcast_resolve` instead of calling this tool.
    ConnectorOAuth
  • Open-ended discovery across SMI deep reports, research bundles, and exports when you do not already have a record id — finds candidates by subject name, url, or keyword and returns typed references to pass to fetch. If you already have a record id from the conversation rather than from a search result, call the specific tool instead: smi_get_deep_report or smi_get_export to read one record, smi_check_order_complete for order readiness, smi_list_deep_reports or smi_list_exports for filtered listings, smi_get_report_findings for findings within a report. Deep reports and research bundles are filtered server-side by subject first/last name, broadening to an unfiltered fetch ranked client-side (across id, name, url, summary) when the filtered fetch finds nothing; exports match on url.
    ConnectorOAuth
  • Fetch one document's full extracted text by id (a file id from search / search_files / list_files), in the deep-research result shape. ALIAS: this is the SAME read as get_file (same data, same permissions, same audit, same size guard - large files are truncated) - use it when your client requires the id/title/text/url fetch contract (ChatGPT deep research); otherwise prefer get_file, which also serves download links and inline images. Read-only; audited.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables deep research tasks using a multi-agent architecture that integrates any LLM and MCP tools. Available via MCP stdio, streamable HTTP, and SSE transports.
    17
    MIT

Matching MCP Connectors

  • One-call profile of a Solana wallet: SOL balance, non-zero SPL holdings, activity window, failure rate, account age, and whether it is a program. Use when you need to judge a counterparty, monitor a treasury, or research a wallet before interacting with it. $0.01 per call in USDC on Solana. Typically returns in under 2s. Read-only. address: Solana wallet address, e.g. Ezk5bEX4VbASmPMdEAvSdtLcW5Dmsgjdy5mdctKkNo1Q
    ConnectorNo auth
  • Trigger a topic snapshot research run. Generates 50 focused prompts on the supplied topic and runs them through the full Trakkr research pipeline (Gemini prompt generation + GPT-4o ranking + competitor normalization). Consumes one of the brand's monthly snapshot credits (5/mo per active brand) — call get_research_credits first to confirm availability. The brand must be active (tracking on). Only use when the user explicitly asks to run new research on a topic. Full prompt research runs are intentionally NOT exposed through the MCP — those run daily on a schedule. The snapshot runs asynchronously (3-5 min). The response returns immediately with a placeholder_id; poll get_research_runs to retrieve the completed payload, or use get_latest_research with report_type='topic_snapshot'. Args: brand_id: The brand to run the snapshot for (required). topic: The topic to focus the snapshot on (2-200 chars, required). topic_context: Optional extra context to refine prompt generation (up to 500 chars).
    ConnectorOAuth
  • Search specific CFR violation citations from FDA inspections (Compliance Dashboard data, not available in openFDA API). Filter by company name, FEI number, CFR number, keyword, program area, fiscal year, inspection date range, or the parent inspection's classification (NAI/VAI/OAI). CFR matching is hierarchical and section-anchored: pass '21 CFR 211.68' or '211.68' and it matches '21 CFR 211.68', '21 CFR 211.68(a)', '21 CFR 211.68(b)' but NOT '21 CFR 211.680' or '21 CFR 211.6'. Each row carries the parent inspection's classification (inspection_classification / inspection_classification_code) joined by inspection_id, plus inspection_id and a best-effort source_url deep link. Returns the cited regulation, short and long descriptions of the finding, and inspection dates. Related: fda_inspections (inspection classification and dates by FEI), fda_search_warning_letters (official warning letters for the same FEI), fda_compliance_actions (warning letters that may reference these citations).
    ConnectorNo auth
  • Scrape a full Wikipedia page (sections, infobox, references). Heavier than lookup/wikipedia. Use for deep research. Example call: {"page": "Anthropic"} Cost: $0.005–$0.05 USDC on Base per call.
    ConnectorNo auth
  • Read a single published research post by post UUID. Use this tool after calling search_research_posts and selecting the most relevant result. The response includes post metadata, authors, sectors, body HTML, and a URL. Depending on the authenticated MCP user's permissions, the body HTML and URL may expose either the full research post or teaser content. Missing, unpublished, and hidden-sector posts return a generic not-found error.
    ConnectorNo auth
  • Researches up to 10 topics in a single call, each with the same full picture as `research_trend`: interest over time, where it is most searched, and related queries. Each topic is looked up on its own scale, so they are not comparable to one another. Use this when you need data across many topics — a long or rich research pass — instead of one tool call per topic. Each section is fetched independently, so a partial result is normal: any section that fails carries an `error` instead of data and the rest still returns.
    ConnectorNo auth
  • Fetches a single SMI deep report by id. Research Bundles are deep-report products, so use this tool for a Research Bundle id too rather than constructing a research_bundle: reference for the generic fetch tool. Accepts product-prefixed ids: RB-11751 (Research Bundle) and DR-11751 (Deep Report) both resolve here.
    ConnectorOAuth
  • Creates a Deep Research task for comprehensive, single-topic research with citations. USE THIS for analyst-grade reports, NOT for batch data enrichment. Use Parallel Search MCP for quick lookups. After calling, share the URL with the user and STOP. Do not poll or check results unless otherwise instructed. Multi-turn research: The response includes an interaction_id. To ask follow-up questions that build on prior research, pass that interaction_id as previous_interaction_id in a new call. The follow-up run inherits accumulated context, so queries like "How does this compare to X?" work without restating the original topic. Note: the first run must be completed before the follow-up can use its context.
    ConnectorOAuth
  • Search official economic statistics by free text, e.g. 'inflation barbados' or 'government debt japan'. Returns result ids that can be passed to fetch. Designed for deep-research connectors; for richer control use get_indicator / get_series.
    ConnectorNo auth
  • Natural-language explanation of a plan_id (what it does) or setting_path (what one setting controls). Audience: merchant (default), developer, or reviewer. Detail: brief (1-2 sentences) or deep (full context + related settings + a11y notes). Use when merchant asks 'what does this do' or 'why this preset'.
    ConnectorNo auth
  • Vaaya's deep reference, FREE and instant. Pass `topic` to get the full playbook for a capability area — exact services, actions, params, prices, model lists, and gotchas — the same reference files the vaaya skill ships. Topics: 'setup' (connecting an agent, a chat app, or an unattended process), 'tools' (exact params of every Vaaya tool, GTM suite included), 'media' (image/video/audio models + product-demo videos), 'gtm' (leads, enrichment, outreach, signals, email), 'research' (OneSearch lanes, deep research, company/market research playbooks), 'data' (scraping, people, social platforms, public records, onchain, compliance), 'compute' (sandboxes, browser automation, files, memory, workers, phone calls, llm). Read the matching topic BEFORE non-trivial work in that area — it is cheaper than a wrong call. Never bills; safe to call any time.
    ConnectorNo auth
  • An end-to-end overview of one management topic: its definition, an in-depth explanation of the discipline, the 3 editor-curated top documents, all known aliases, document and case study counts, related topics, and the topic page URL. Use this to survey a discipline before going deep — e.g. "what does Digital Transformation cover and what are its key frameworks" — or to orient when the user describes a broad problem area. Follow with search_content (topic filter) for the full catalog.
    ConnectorNo auth
  • Semantic (vector similarity) search across blog posts and projects — the same Cloudflare Vectorize retrieval the Ask chatbot uses, without the LLM call. Broader than search_posts (which only does exact substring matching on title/description/tags): finds conceptually related content even when the query words never appear verbatim. Returns scored chunks with deep-link URLs.
    ConnectorNo auth
  • Search SearchShopAI's Research Notes blog — data studies, playbooks, and field notes on agentic commerce (AI attribution, MCP, AI catalog accuracy, ChatGPT ads). Returns matching articles with titles, summaries, and URLs. Use when asked what SearchShopAI has written or published about a topic.
    ConnectorNo auth
  • Search SearchShopAI's Research Notes blog — data studies, playbooks, and field notes on agentic commerce (AI attribution, MCP, AI catalog accuracy, ChatGPT ads). Returns matching articles with titles, summaries, and URLs. Use when asked what SearchShopAI has written or published about a topic.
    ConnectorNo auth