Flexreport Finance

get_aftermarket_data

Read-only

Query STORED after-hours 15-minute bars (open/high/low/close/volume) for symbols.

Returns the extended-hours bars the backend has captured for `symbols` — one row per
symbol per 15-minute bar, 16:00-20:00 ET, ordered by symbol then bar time DESC (so the
first row per symbol is the latest bar). This is the recorded aftermarket tape, NOT a
live feed; it is polled every 15 minutes from 16:30 ET through the evening, so a bar
can lag the wall clock by up to ~15 minutes. For a live intraday read of the regular
session use `detect_intraday_outlier_jumps` instead.

Leave both datetimes off for "today's aftermarket tape". An empty `bars` list means no
bars were captured in the window (e.g. before 16:30 ET, or on a non-trading day) — not
an error.

Requires auth (your MCP client attaches the OAuth bearer automatically). Rate-limited
to 300/minute per user server-side.

Input Schema

TableJSON Schema

Name	Required	Description
`symbols`	Yes	Covered tickers, e.g. ["AAPL", "MSFT"].
`end_datetime`	No	Inclusive upper bound on bar time, ET wall-clock ISO-8601. Omit for 23:59:59 today ET.
`start_datetime`	No	Inclusive lower bound on bar time, ET wall-clock ISO-8601 ("2026-06-24T16:00:00"). Omit for 00:00:00 today ET.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bars`	Yes	One row per symbol per 15-min bar, 16:00-20:00 ET, ordered by symbol then time DESC (first row per symbol is the latest). Empty means no bars were captured in the window.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Although annotations already declare readOnlyHint=true, the description adds substantial context: the data is a stored tape rather than a live feed, it is polled every 15 minutes from 16:30 ET with up to ~15 min lag, the 16:00-20:00 ET window and row ordering, plus auth (OAuth bearer) and a 300/min rate limit.

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?

Front-loads the core purpose in the first sentence, then layers scope, caveats, defaults, and edge cases as separate short paragraphs. No sentence is redundant, and the sibling reference is placed at the point of contrast.

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, and the description nonetheless covers the operational profile an agent needs: stored/lagged semantics, time window, ordering, defaults, empty-result behavior, auth, and rate limits.

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 100% and both datetime defaults are already documented in the schema, so the baseline is 3. The description still adds interpretive value by framing omitting both datetimes as 'today's aftermarket tape' and by explaining the sort order (symbol then bar time DESC, latest first) that shapes how the params return data.

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 resource with scope: 'Query STORED after-hours 15-minute bars (open/high/low/close/volume) for symbols.' It explicitly distinguishes itself from the sibling detect_intraday_outlier_jumps by contrasting the recorded aftermarket tape with a live intraday read.

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?

Names the alternative tool and the condition that selects it ('for a live intraday read of the regular session use detect_intraday_outlier_jumps instead'), and gives explicit guidance on omitting datetimes for today's tape. It also pre-empts a common confusion by stating an empty bars list is not an error.

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?