Skip to main content
Glama
haiyunsky

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

get_ai_prediction

Get a data-driven probability estimate for the next trading day's direction using an ensemble of gradient-boosted trees, LSTM, and quantum-classical hybrid models. Delivers up/down prediction, confidence, and model votes.

Instructions

Get an AI/ML directional prediction for a stock's next-session move.

Use this tool when:

  • You want a data-driven probability estimate for the next trading day's direction (up vs. down).

  • You need the individual model votes (ensemble breakdown) to assess consensus strength.

  • You want to compare model confidence against current IV pricing.

The prediction engine uses an ensemble of gradient-boosted trees, an LSTM, and a VQC (quantum-classical hybrid) model. Features include VIX, relative strength, Treasury rates, and options flow signals.

Parameters

symbol : str Exchange ticker in uppercase, e.g. "NVDA", "META", "QQQ". Per-ticker model accuracy varies; META and QQQ have shown above- baseline hit rates in backtests.

Returns

dict with keys: symbol : str — normalized ticker prediction : str — "Up" | "Down" | "Neutral" up_probability : float — 0.0–1.0 probability of upward close confidence : float — 0.0–1.0 ensemble agreement score model_votes : dict — per-model predictions and probabilities regime : str — "Bull" | "Bear" | "Chop" market regime signal_strength : str — "Strong" | "Moderate" | "Weak"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesExchange ticker in uppercase, e.g. 'NVDA', 'META', 'QQQ'. Do NOT pass company names — use official tickers only. Per-ticker model accuracy varies; META and QQQ have shown above-baseline hit rates in backtests.
Behavior4/5

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

Describes ensemble models (GBM, LSTM, VQC), input features (VIX, rates, options flow), and per-ticker accuracy variation. No annotations to contradict; detailed behavioral disclosure.

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?

Well-structured with sections for usage, engine details, parameters, and returns. No extra fluff; every sentence contributes. Slightly lengthy return description is justified by missing output schema.

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?

No output schema, so the description fully documents all return fields (symbol, prediction, probabilities, votes, regime, signal strength). Also covers model details and accuracy caveats, making the tool self-contained.

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?

Single parameter symbol has 100% schema coverage. Description adds 'Do NOT pass company names' and notes META/QQQ have better hit rates, providing extra beyond 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?

Specific verb+resource+scope: 'Get an AI/ML directional prediction for a stock's next-session move'. Clear action and outcome, distinct from sibling tools like get_iv_radar or get_monte_carlo.

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?

Provides explicit 'Use this tool when' scenarios: need probability estimate, ensemble breakdown, or compare confidence to IV pricing. Could mention alternatives but offers actionable context.

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