Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

research_bundle

[$1.00] Composite executive research dossier (Stripe card-eligible). Runs web search, breaking news, SEC company intelligence, and optional URL extraction in parallel in one call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "research_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias of query
urlNoOptional public URL to extract clean text from
limitNoMax search and news results each (default 10)
queryNoResearch topic or query (required; alias: q)
tickerNoOptional stock ticker for SEC EDGAR company intel (e.g. NVDA)
synthesizeNoAdd one LLM synthesis across all sources (default true)
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral facts: a $1.00 charge, parallel fan-out across four sources, and that URL extraction is optional. However it says nothing about what the returned dossier actually looks like, error behavior when one sub-source fails, or whether the charge applies on degraded/timeout responses — a notable gap for a paid composite.

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?

Two compact sentences with the cost and the composition front-loaded before the detail. The '[Stripe card-eligible]' parenthetical is the only arguably low-value token, but it is legitimate billing context rather than filler.

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?

For a 7-parameter, paid, multi-source aggregator with no output schema and no annotations, the description is thin: it never characterizes the dossier's structure or sections, which is the main thing an agent needs to decide whether this replaces several single-source calls. Cost and parallelism are covered, but return shape and required-input expectation are left to the schema.

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 coverage is 100% and each parameter already carries a description, so the schema does the heavy lifting. The description only reinforces that URL extraction is optional and that the tool spans search/news/SEC, without adding format, interaction, or mutual-exclusion semantics (e.g. query vs q, limit applying to search and news separately).

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?

States a specific composite verb set and resource: web search, breaking news, SEC company intelligence and optional URL extraction, combined into an 'executive research dossier'. The 'in one call' / 'parallel' framing distinguishes it from single-source siblings like search, news and company. It stops short of naming the near-duplicate sibling research_dossier, so the differentiation is incomplete.

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?

Implies the right context (multi-source executive research in a single round trip) but never states when to prefer it over calling search/news/company individually, nor when a lighter or cheaper alternative is preferable. No exclusions, prerequisites, or guidance on when the $1.00 composite cost is worth it versus single-source tools.

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