Skip to main content
Glama

Deep research

deep_research
Read-onlyIdempotent

Deep research. 1-Call Deep Web Research & Verified Citation Engine: queries Wikipedia, HackerNews, and ArXiv in parallel and synthesizes an executive brief, bulleted key facts, numbered URL citations [1..N], and an Ed25519 provenance receipt. Free playground: https://apexfaucet.xyz/memory/ . $0.003 per call over x402 or X-API-Key.

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": "deep_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesResearch question or topic (3-240 chars).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
maxSourcesNoMaximum verified citations to return (3-12, default 6).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts: exactly which three upstream sources are hit, that they run in parallel, that one call returns brief + bullet facts + numbered URL citations [1..N] + an Ed25519 provenance receipt, and that access is metered through x402 or an X-API-Key. It omits failure/degradation behavior when a source is unreachable, which keeps it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and the core capability is front-loaded, but it is delivered as a single run-on string with colon-and-ampersand stacking, and the 'Free playground: https://...' promo plus price tag read as marketing rather than invocation guidance. Nothing is redundant, but the structure makes the operational facts harder to extract than they need to be.

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

Completeness4/5

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

With no output schema, the description correctly compensates by enumerating the return artifacts (brief, key facts, numbered citations, provenance receipt), and the payment model is spelled out for a metered open-world tool. Source-coverage limits and behavior when a source returns nothing are the notable omissions, so it is strong but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so query, payment, and maxSources are already documented with types and defaults, making 3 the baseline. The description adds only marginal semantics, chiefly that payment is a metered $0.003 charge via x402 or X-API-Key, which clarifies why the payment parameter exists but gives no payload format or default-payment behavior.

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 names a concrete verb and resource cluster: it 'queries Wikipedia, HackerNews, and ArXiv in parallel and synthesizes an executive brief' with citations. That is far more specific than the title 'Deep research' and implicitly separates it from single-source siblings like paper_search or page_extract, but it never names a sibling or a boundary, so it stops short of a 5.

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?

There is no when-to-use / when-not-to-use guidance and no named alternative among the large sibling set. The only decision-relevant context is commercial (free playground plus $0.003 per call via x402 or X-API-Key), which tells an agent the call is metered but not when to prefer it over paper_search or site_extract.

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.

Resources