Skip to main content
Glama
haiyunsky

Quant Finance MCP Server for Stock Analysis and Options Analytics - HPSILab

generate_stock_research_report

Generate a comprehensive stock research report with AI predictions, volatility analysis, options positioning, Monte Carlo outlook, and strategy backtests in institutional markdown format.

Instructions

Generate a structured, institutional-style markdown research report for a single stock, covering all major quantitative signal sources.

The report is divided into six sections:

  1. Executive Summary — bull/bear verdict, confidence score, one-line thesis

  2. AI Prediction — ensemble model votes, up-probability, regime

  3. Volatility Analysis — ATM IV, IV rank, vol regime, risk reversal

  4. Options Positioning — max pain, gamma wall, expected move, squeeze targets

  5. Monte Carlo Outlook — 30-day price distribution, 90 %/68 % confidence ranges

  6. Strategy Backtests — Sharpe, max drawdown, win rate across quant strategies

Output is a complete markdown string (~800–1200 words) ready to render or share. Response latency is ~10–20 s due to full multi-model data aggregation.

Use this tool when:

  • A user asks for a "report", "write-up", "research note", or "deep dive".

  • You want a pre-formatted narrative combining all signal sources in one document.

  • You need output suitable for archiving, PDF export, or investor communication.

Do NOT use this tool when:

  • You only need a quick directional verdict → use analyze_stock instead.

  • You need a specific data dimension (IV, Monte Carlo, etc.) → use the dedicated sub-tool (get_iv_radar, get_monte_carlo, etc.) for lower latency.

Parameters

symbol : str Exchange ticker in uppercase, e.g. "NVDA", "TSLA", "SPY". Do NOT pass company names — use official tickers only.

Returns

dict with keys: symbol : str — normalized ticker report : str — full markdown report (~800–1200 words, 6 sections) generated_at : str — ISO 8601 generation timestamp

Notes

  • Requires a valid HPSILAB_API_KEY.

  • Free-tier keys are limited to a predefined ticker set.

  • For programmatic use, prefer analyze_stock which returns structured JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses output format (markdown, ~800-1200 words, 6 sections), latency (~10-20s), API key requirement, and return structure. Fully transparent.

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

Conciseness5/5

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

Well-structured with sections, bullet points, and clear language. Front-loaded with summary and breakdown of sections. Every sentence is informative and earns its place.

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?

Comprehensive for a complex tool with 6 sections. Explains report contents, output format, prerequisites, and return parameters. No output schema, but return dict keys are described.

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

Parameters5/5

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

Single parameter 'symbol' is described with clear instructions: uppercase ticker, no company names. Schema coverage is 0%, so description adds essential meaning beyond the schema.

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?

Clearly states it generates a structured institutional-style markdown research report for a single stock, covering all major signal sources. Differentiates from sibling tools like analyze_stock and sub-tools.

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?

Explicitly states when to use (user asks for report, write-up, deep dive) and when not (quick verdict or specific data dimension), with named alternatives (analyze_stock, get_iv_radar, etc.).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/haiyunsky/hpsilab-quant-finance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server