Skip to main content
Glama

Rolling price-action events

quantdata_brooks_events
Read-only

Classical Brooks price-action events detected in the current trading window — the day's first range breakout, breakout follow-through, closes in the top or bottom third of an established range, long-lived-range breakouts, climactic spikes — each paired with the outcome rate measured for that exact definition in that exact window (pre-registered, ES 5-minute bars 2010-2026). Range breakouts also carry a calibrated per-event estimate of the probability the breakout closes back through its level within 10 bars (validated zero-shot on NQ 2023+: AUC 0.646, calibration error 5.1%, n=2,637). Answers 'what just happened structurally, and how did events like it resolve historically'. Works around the clock on 24-hour instruments, including the Asia-close-to-US-open gap window. Some measured rates contradict the classical claims; quote the measured numbers, not the folklore. Every read also carries two blocks that answer different questions and must not be mixed: day_type is the five-class day-type distribution, from the model trained for the current window. In the regular day session it is mode=day_session, with published accuracy: 66% top-1 over a complete session and 53.5% at the 90-minute mark, against a 37% majority-class baseline. In the Asian window it is mode=asia_session — trained natively on Asian windows, pre-registered, confirmed zero-shot on NQ — whose accuracy figures live in the response's own accuracy field and use their own label taxonomy: never quote the day-session figures for an asia read or vice versa. The gap window has no validated model and returns available=false there. shape is plain arithmetic over the bars already printed (where price closed inside its own range, how much of the travel was one-way, deepest pullback) — no model, no accuracy claim, available in every window including the gap. Report day_type as a distribution with its baseline; report shape as measurement, never as a forecast. day_type.analysis is the block to lead with (day-session reads only; the asia_session read carries no analysis layer) — it answers 'should today's read be trusted at all' before it answers 'what is today'. It carries: confidence (the model's own conviction crossed with how consistently the most similar past sessions resolved — both high has been right 95% of the time, both low only 41%, against a 66% baseline; say which bucket today falls in and stop treating a low-confidence read as a call); live_now (patterns mechanically confirmed on today's bars so far — e.g. 'broke yesterday's low then reclaimed it = bear trap confirmed' — this is what actually happened, trust it over any statistical checklist); what_to_watch (patterns over-represented on this day type, each with a status_today of yes/no/forming/unknown and a concrete way to verify it intraday; use the ordering, not the raw lift decimals); and summary / summary_zh, a one-line verdict written to be relayed verbatim — if you pass along only one sentence, pass that one. Descriptive statistics — not a recommendation. Check window_is_live before calling a read 'now'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTicker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Resolve names to tickers first: gold is GC=F (COMEX futures) or GLD (the ETF) — not GOLD, which is a US-listed equity (Gold.com, Inc.). Spot gold itself has no feed here; a request for XAUUSD answers with the XAUT-USD token reading and says so. XAUT-USD is the Tether Gold token's order book, a different instrument from spot gold — relay its notes when you use it.
windowNoOmit to follow whichever window has the freshest bars — usually what the user means by 'now'. 'rth' is the US day session; 'gap' is 16:00-21:30 Beijing, the stretch between the Asian close and the US open; 'asia' is 09:00-16:00 Beijing. gap and asia exist for 24-hour instruments (futures, FX, crypto) only. Every window carries its own pre-registered reference rates — the response pairs each event with the rates measured for the window it fired in.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Resolve names to tickers first: gold is GC=F (COMEX futures) or GLD (the ETF) — not GOLD, which is a US-listed equity (Gold.com, Inc.). Spot gold (XAUUSD) is not covered. XAUT-USD is the Tether Gold token's order book, a different instrument from spot gold — send it only when the user asked for tokenised gold."New value: +"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Resolve names to tickers first: gold is GC=F (COMEX futures) or GLD (the ETF) — not GOLD, which is a US-listed equity (Gold.com, Inc.). Spot gold itself has no feed here; a request for XAUUSD answers with the XAUT-USD token reading and says so. XAUT-USD is the Tether Gold token's order book, a different instrument from spot gold — relay its notes when you use it."
  2. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Spot gold as XAUUSD. Resolve names to tickers first: gold is XAUUSD (spot), GLD (ETF) or GC=F (futures) — not GOLD, which is a US-listed equity (Gold.com, Inc.). XAUT-USD is the Tether Gold token's order book, a different instrument from spot gold — send it only when the user asked for tokenised gold."New value: +"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Resolve names to tickers first: gold is GC=F (COMEX futures) or GLD (the ETF) — not GOLD, which is a US-listed equity (Gold.com, Inc.). Spot gold (XAUUSD) is not covered. XAUT-USD is the Tether Gold token's order book, a different instrument from spot gold — send it only when the user asked for tokenised gold."
  3. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Spot gold as XAUUSD. Resolve names to tickers first: gold is XAUUSD (spot), GLD (ETF) or GC=F (futures) — not GOLD, which is a US-listed equity (Gold.com, Inc.)."New value: +"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Spot gold as XAUUSD. Resolve names to tickers first: gold is XAUUSD (spot), GLD (ETF) or GC=F (futures) — not GOLD, which is a US-listed equity (Gold.com, Inc.). XAUT-USD is the Tether Gold token's order book, a different instrument from spot gold — send it only when the user asked for tokenised gold."
  4. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Resolve names to tickers first: gold is GLD or GC=F, not GOLD — GOLD is Barrick, the mining company."New value: +"Ticker. US stocks and ETFs as-is (NVDA, SPY). US futures with =F (ES=F, GC=F). Hong Kong as digits.HK (3690.HK). China A-shares as 6 digits (600519). Crypto as PAIR-USD (BTC-USD). Spot FX with no slash (EURUSD). Spot gold as XAUUSD. Resolve names to tickers first: gold is XAUUSD (spot), GLD (ETF) or GC=F (futures) — not GOLD, which is a US-listed equity (Gold.com, Inc.)."
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnlyHint and openWorldHint, so the description's job is to add operational context. It discloses pre-registration, local measured rates that may contradict folklore, the separate day_type and shape blocks, the missing model in the gap window, the confidence-bucket behavior, and the instruction to lead with day_type.analysis. This is rich, non-contradictory disclosure far beyond the annotations.

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?

The description is long but high-density: every sentence carries a distinct fact or caution. The bolded lead block and clear separation of day_type/shape/analysis improve scannability. However, the inline, paragraph-style formatting makes it harder to navigate than bulleted sections would be, and a few warnings (e.g., 'do not mix') are repeated in multiple forms.

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?

With no output schema, the description must explain return values, and it does so thoroughly. It covers the day_type and shape blocks, the fields inside analysis (confidence, live_now, what_to_watch, summary), the asia-specific accuracy field, the available=false case for the gap window, and the proper way to relay the summary. This is complete for a complex tool.

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?

Schema coverage is 100%, but the description adds substantial meaning beyond the schema. For the symbol parameter it explains resolution pitfalls (GOLD is an equity, gold is GC=F or GLD, XAUT-USD substitution for spot gold) and for the window parameter it explains which instruments support gap and asia and how each window's rates are pre-registered. This is not mere repetition; it is essential disambiguation.

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?

The description clearly states the tool detects classical Brooks price-action events in the current trading window and pairs each with historical outcome rates. It answers a specific question—'what just happened structurally, and how did events like it resolve historically'—and is obviously distinct from sibling tools like gamma, max_pain, and weis_wave.

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?

The description provides clear usage context: it works around the clock on 24-hour instruments, explains the rth/gap/asia window semantics, and tells when a window returns unavailable. It even warns against mixing accuracy figures between day-session and asia-session reads. However, it never explicitly names sibling tools as alternatives or says 'when not to use this tool,' so it stops short of full exclusion guidance.

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.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct market data domain: Brooks price action events, dealer gamma, options max pain, API key request, and Weis Wave volume-price structure. Despite some conceptual overlap between options-related tools, their descriptions clearly differentiate calculations and data sources.

Naming Consistency5/5

All five tools follow the exact same `quantdata_<topic>` snake_case pattern, making the naming perfectly uniform and predictable. No mixed conventions or stylistic deviations.

Tool Count5/5

Five tools is a well-scoped set for a specialized quant data server. Each tool serves a clear analytical purpose, and the API key request tool supports access to the four data tools without bloating the surface.

Completeness5/5

The set explicitly covers four market-data categories plus key management, and each tool is fully self-contained for its intended analysis. No obvious dead ends or missing core operations within the stated domain of quantitative market analytics.