Skip to main content
Glama

HPSILab Quant Finance

Monte Carlo Simulation

get_monte_carlo
Read-onlyIdempotent

Monte Carlo price simulation for the next ~10 trading days: thousands of random price paths estimate a likely price range and the odds of finishing higher.

Returns the price-history date and starting close, mean and median
projected close, the 90% range, daily volatility, support/resistance and
the chance of finishing above resistance. It also returns the simulated
distribution of day-10 closes: percentiles (p5-p95), a 40-bin histogram
(price range and path count per bin) and a Gaussian KDE curve on the same
count scale - enough to chart the distribution as a histogram with the 90%
range, mean and resistance marked. The simulation is seeded from the price
history, so repeated calls on the same data return the same numbers.

Args:
    ticker: Stock symbol, e.g. "AAPL".

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": {
      "ticker": "<ticker>"
    },
    "name": "get_monte_carlo"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol, e.g. AAPL.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive status, yet the description adds real behavioral content: the ~10-day horizon, the simulation's seeded determinism ('repeated calls on the same data return the same numbers'), and the fact that history drives the simulation. It stops short of stating failure behavior for an invalid or history-less ticker.

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?

Front-loaded with the core purpose, then a long second paragraph enumerating return fields. The length is largely justified because there is no output schema, though the return-value enumeration could be tightened slightly without losing meaning.

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 and only one parameter, the description carries the burden of explaining returns and does so thoroughly, including the histogram/KDE charting detail. What is missing is minimal: behavior on invalid tickers or absent price history, and whether history is fetched internally.

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?

There is a single required parameter with 100% schema description coverage and an example, so the schema already does the work. The description's 'ticker: Stock symbol, e.g. "AAPL"' merely restates it and adds no exchange, casing, or format constraints.

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 verb and resource ('Monte Carlo price simulation') together with the horizon ('next ~10 trading days') and the method ('thousands of random price paths'), so the operation is unambiguous. It does not explicitly contrast itself with siblings like get_ai_prediction or get_equity_curve, leaving that differentiation to inference from the distinctive wording.

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?

Usage is only implied: an agent can infer this is for estimating a forward price range and probability of gain over a short horizon. There is no explicit when-to-use, when-not-to-use, or named alternative such as the AI prediction or equity curve 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.