Skip to main content
Glama

HPSILab Quant Finance

Stock Research Report

generate_stock_research_report

Full markdown research report with its most relevant stock-report charts attached as images. Pro tool ($0.35/call via x402 for anonymous callers; free within plan limits for signed-in accounts, subject to a monthly report quota).

Runs analyze_stock and stock-report image generation concurrently, then
renders a presentation-ready markdown report (direction, direction score, bullish /
bearish factors, source-tool status). The one or two most relevant charts are
attached as PNG image content; the markdown is returned for display and the
same data, with chart URLs, is mirrored in structured JSON.

Signed-in hpsilab users call this within their plan's free rate limits.
Anonymous / tokenless agents pay per call via x402 (USDC on Base) when
payments are enabled — send the x402 payment in the request _meta.

Args:
    symbol: Stock symbol, e.g. "RXRX".
    refresh: Bypass the backend's fresh IV cache for the IV-driven modules.
        Defaults to False.
    force_images: Force a fresh image render instead of reusing the backend's
        image cache. Defaults to False.

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": {
      "symbol": "<symbol>"
    },
    "name": "generate_stock_research_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol, e.g. AAPL.
refreshNo
force_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / symbol / description
      Added value: +"Stock ticker symbol, e.g. AAPL."
    • addedInput schema / properties / symbol / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say it is non-read-only, open-world, non-idempotent and non-destructive; the description goes well beyond that by disclosing cost and payment mechanics (x402, USDC on Base, _meta placement), quota limits, and the internal concurrency model. It also describes the return surface (markdown for display, one or two PNG charts, mirrored structured JSON with chart URLs) and the caching semantics behind refresh and force_images.

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 Args block and the concurrency paragraph are well organized, but pricing and access rules are stated twice — once in the opening 'Pro tool ($0.35/call via x402...)' parenthetical and again in the standalone paragraph about signed-in users and anonymous x402 payers. That duplication inflates the length of what is otherwise a tight definition.

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 no output schema, the description carries the full burden and discharges it: it specifies the three return channels (markdown, PNG image content, mirrored JSON with chart URLs), the report's internal fields (direction, direction score, bullish/bearish factors, source-tool status), payment/auth requirements, and per-parameter caching effects. An agent has everything needed to call it and interpret the result.

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 only 33% — refresh and force_images carry no schema descriptions — so the description must compensate, and it does: refresh is explained as bypassing the backend's fresh IV cache for IV-driven modules, and force_images as forcing a re-render instead of reusing the image cache. The symbol parameter is merely restated from the schema, and 'IV-driven modules' is left as unexplained jargon, keeping it just below a 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 verb and artifact: renders a presentation-ready markdown research report with the most relevant stock-report charts attached as PNGs, and explicitly names the source operations it composes (analyze_stock plus stock-report image generation). This distinguishes it cleanly from the analyze_stock and generate_stock_images siblings.

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

Usage Guidelines4/5

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

Gives clear context for who should call it and under what commercial terms: signed-in plan users get free rate-limited access, anonymous/tokenless agents pay $0.35/call via x402 with the payment supplied in request _meta, and there is a monthly report quota. It stops short of an explicit routing rule such as 'use this instead of calling analyze_stock and generate_stock_images separately', which would be the final missing piece.

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.