Skip to main content
Glama

Deep Research

research
Read-only

Multi-step deep research: search, scrape, enrich entities, and synthesize into a cited report. Returns a report (title, summary, sections, key findings, confidence) with numbered sources and the people and companies it found, enriched. Use for a question that needs many sources and a synthesized, cited answer. It takes far longer and costs more than search, which suits a quick fact. Cost: standard 10 credits, deep 20 credits, comprehensive 35 credits, charged only when a call succeeds. Options change it: include_analysis true +5, academic in source_types +2, enrich_entities false -3, synthesis false -5.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "research"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoResearch depth.standard
queryYesThe research question or objective.
freshnessNoTime filter for search results.any
synthesisNoGenerate a synthesized report. Set false for raw mode (sources + entities only).
max_sourcesNoMaximum number of sources to collect.
source_typesNoComma-separated source types: web, news, academic.web
enrich_entitiesNoEnrich detected people and companies with profile and firmographic data.
include_analysisNoGenerate computational analysis with charts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-destructive), it discloses cost per depth tier (10/20/35 credits), per-option cost deltas, and the billing rule that charges occur only on success — information an agent cannot get from annotations. It also discloses the latency profile ("takes far longer") and the return shape in the absence of an output schema.

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?

Front-loaded with what the tool does and what it returns, then usage guidance, then a compact cost ledger. The final cost sentence is dense and list-like but each item carries decision-relevant information; nothing is filler.

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?

With 8 parameters and no output schema, the description covers purpose, routing, return shape, latency and cost — everything an agent needs to decide and invoke correctly. No meaningful gap remains for a research tool.

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 coverage is 100%, so the baseline would be 3; the description earns extra by attaching concrete consequences to specific options — include_analysis +5 credits, academic source_type +2, enrich_entities false -3, synthesis false -5. It stops short of explaining semantics for depth tiers or max_sources beyond cost, so not a full 5.

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?

States a specific multi-step pipeline (search, scrape, enrich, synthesize) and the concrete artifact produced: a cited report with title, summary, sections, key findings, confidence, numbered sources and enriched entities. It explicitly names the sibling it differs from (search) and the axis of difference (depth/time/cost).

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ("a question that needs many sources and a synthesized, cited answer") and a when-not-to-use with the named alternative ("search, which suits a quick fact"). The trade-off in latency and cost is spelled out so the agent can route correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.