Skip to main content
Glama

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

research_dossier

[$1.00] Compile a pre-digested, vector-ready intelligence pack for any ticker, topic, or sector with executive summary, SEC XBRL financial highlights, risks, and Markdown chunks.

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_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias of query
queryNoCompany ticker, topic, or industry sector (required; alias: q, target)
targetNoAlias of query
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.2/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 behavioral burden, and it does disclose one important trait: a $1.00 cost, which is real selection-relevant context. It also implies the output is pre-chunked/vector-ready, which hints at return shape. However, it says nothing about permissions, rate limits, whether the operation is read-only, or what 'degraded' responses mean (that detail lives only in the 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?

A single sentence with the price tag front-loaded, followed by the output contents in priority order. Nothing is redundant, though the phrase 'pre-digested, vector-ready' is marketing-flavored rather than informative and the list could be tightened.

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 does the work of enumerating return sections, which is the right call, and it flags cost. What is missing is routing context against the many overlapping research/briefing siblings, which matters for a fairly complex aggregator. Timeout/degraded semantics are covered by the schema, so that gap is acceptable.

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/q/target aliases and the timeout_ms degraded-mode contract are already documented in structured fields. The description adds no syntax, format, or ambiguity resolution beyond noting the accepted subject types (ticker/topic/sector), which overlaps the schema's own 'query' description. Baseline 3 is appropriate.

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?

Uses a specific verb ('Compile') with a concrete artifact ('pre-digested, vector-ready intelligence pack') and enumerates the sections produced: executive summary, SEC XBRL financial highlights, risks, Markdown chunks. It clearly states input scope (ticker, topic, or sector), so an agent knows what it produces. It does not differentiate from the sibling research_bundle, which reads like a near-overlapping offering.

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 or when-not-to-use guidance and no mention of alternatives such as research_bundle, topic_briefing, or company. The only scope hint is 'for any ticker, topic, or sector,' which describes coverage rather than selection criteria. An agent must infer routing from the noun phrase alone.

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