Flexreport Finance

detect_intraday_outlier_jumps

Read-only

Live look at TODAY's intraday tape, flagging outlier price jumps.

Pulls today's intraday bars for `symbol` (US/Eastern trading day) live at the given
`frequency` and flags each bar whose move is a statistical outlier versus the stock's
own daily-return volatility — i.e. bars where |z-score| of the move exceeds
`zscore_threshold`. Use it for a quick "is the stock making an abnormal intraday move
right now?" read.

Synchronous — returns the flagged bars directly (no task id to poll). Returns a
404-style error if no intraday data is available yet (e.g. before the market opens or
for an uncovered symbol).

Requires auth (your MCP client attaches the OAuth bearer automatically).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Covered ticker, e.g. "AAPL".
`frequency`	No	Intraday bar size; list_options(kind="intraday_frequency") lists the supported values.	one_minute
`zscore_threshold`	No	Daily-sigma cutoff for flagging a bar: higher = stricter (fewer, more extreme flags), lower = more sensitive.

Output Schema

TableJSON Schema

Name	Required	Description
`latest`	No	The most recent bar.
`series`	Yes	Every bar today, ascending by time.
`symbol`	Yes
`outliers`	Yes	Bars with \|z-score\| >= zscore_threshold.
`prior_close`	No	Prior session's close, the return baseline.
`most_extreme`	No	Today's bar with the largest \|z-score\|.
`daily_std_20d`	No	Std dev of the trailing 20 daily log returns (the sigma).
`daily_mean_20d`	No	Mean of the trailing 20 daily log returns.
`is_outlier_now`	Yes	True when the latest bar is beyond the threshold.
`zscore_threshold`	Yes	The \|z\| cutoff applied.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint annotation: synchronous execution with no task id to poll, direct return of flagged bars, a 404-style error when no intraday data exists yet, and automatic OAuth bearer attachment. These are exactly the operational facts an agent needs before calling.

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 live-today purpose, then mechanics, then error/auth notes. Every sentence carries information, though it runs slightly long for three parameters.

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?

An output schema exists, so return values need not be described; the description nonetheless covers the synchronous contract, the failure mode, and auth. Nothing an agent needs to invoke this correctly is missing.

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 already 100%, so the baseline is 3, but the description adds real meaning: moves are scored against the stock's own daily-return volatility, the day is US/Eastern, and frequency is defined as the intraday bar size. Z-score semantics are clarified beyond the schema's terse 'Daily-sigma cutoff'.

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+resource+scope: pulls TODAY's live intraday bars for a symbol and flags bars whose |z-score| exceeds a threshold. It is clearly distinguishable from siblings like get_technical_indicator_data, get_aftermarket_data, and get_company_snapshot.

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 a clear usage context ('quick is the stock making an abnormal intraday move right now? read') and implicitly scopes to live/today rather than historical analysis. It does not, however, name a sibling alternative or state when NOT to use it (e.g. after-hours vs. get_aftermarket_data).

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

All Flexreport Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?