Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get RVOL History

get_rvol_history
Read-only

Retrieve per-day relative-volume (RVOL) history for a ticker by trading session, comparing each session to its trailing same-session baseline to reveal unusual volume surges.

Instructions

Get the per-day relative-volume (RVOL) time series for a ticker, bucketed by trading session (premarket 04:00-09:30 ET, regular 09:30-16:00, afterhours 16:00-20:00, or all four). Each day's RVOL compares that session's volume to a trailing same-session baseline (30 trading days by default, configurable via "baselineDays"), so premarket volume is judged against premarket history (not a stale full-day figure); the series shows unusual premarket / session volume surges over the last N days. Each point also carries "baselineState": "ready" (rvol is populated), "warming" (baseline not yet warm), "no-cutoff-history" (established ticker that never traded at this session/cutoff before) or "no-history" (new listing, no prior trading history at all), so a null rvol is explained rather than silent. Points additionally carry "advRatio" (that day's volume / the trailing 30-session average full-day volume, null when no full-day denominator exists) and "advDays" (its sample size), which give a magnitude to points RVOL cannot rate. advRatio is not an RVOL: it compares a partial session to a whole day, so it is typically well under 1 and is not comparable to rvol.

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_rvol_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of trailing calendar days of history (1–90, default 30).
tickerYesStock ticker symbol (e.g., "AAPL", "TSLA")
sessionNoOne session bucket; unset returns all four sessions.
asOfTimeNoOptional true time-of-day premarket basis. Any HH:MM ET premarket time; snapped to the nearest 15-minute grid cutoff (04:00–09:15, ties resolve to the earlier cutoff). When set, the series is the premarket as-of RVOL: cumulative volume known by that cutoff / the trailing baselineDays (default 30) average of the same cutoff (not the full 04:00-09:30 session). Forces the premarket session; any "session" argument is ignored. Each point carries a "basis" field: the snapped cutoff actually used ("asof-0700"), or "full-session" for dates with no precomputed as-of row. Unset means the standard full-session series.
baselineDaysNoRolling RVOL baseline window, in trading rows (same-session days). Default 30; values outside 20-250 are clamped. This is the DENOMINATOR window: every RVOL in the response is that period's volume divided by the average of the trailing N same-session (or same-cutoff) days, excluding the day itself. A SHORTER window tracks recent regime changes faster and is noisier; a LONGER one is smoother and slower to react. The warm-up lookback scales with it automatically, so a wide window is never under-filled into an inflated ratio; the minimum-warm-days gate (20 prior sessions) does NOT scale down, so at the 30-row default a ticker needs 20 of its last 30 sessions populated before rvol is non-null. Unset means the standard 30-day baseline; 90 reproduces the pre-2026-09 window.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.20.0
    • changedInput schema / properties / asOfTime / description
      Previous value: -"Optional TRUE time-of-day premarket basis. Any HH:MM ET premarket time; snapped to the nearest 15-minute grid cutoff (04:00–09:15, ties resolve to the earlier cutoff). When set, the series is the PREMARKET as-of RVOL: cumulative volume known BY that cutoff ÷ the trailing baselineDays (default 30) average of the SAME cutoff (not the full 04:00–09:30 session). Forces the premarket session — any \"session\" argument is ignored. Each point carries a \"basis\" field: the snapped cutoff actually used (\"asof-0700\"), or \"full-session\" for dates with no precomputed as-of row. Omit for the standard full-session series."New value: +"Optional true time-of-day premarket basis. Any HH:MM ET premarket time; snapped to the nearest 15-minute grid cutoff (04:00–09:15, ties resolve to the earlier cutoff). When set, the series is the premarket as-of RVOL: cumulative volume known by that cutoff / the trailing baselineDays (default 30) average of the same cutoff (not the full 04:00-09:30 session). Forces the premarket session; any \"session\" argument is ignored. Each point carries a \"basis\" field: the snapped cutoff actually used (\"asof-0700\"), or \"full-session\" for dates with no precomputed as-of row. Unset means the standard full-session series."
    • changedInput schema / properties / baselineDays / description
      Previous value: -"Rolling RVOL baseline window, in trading rows (same-session days). Default 30; values outside 20-250 are clamped. This is the DENOMINATOR window: every RVOL in the response is that period's volume divided by the average of the trailing N same-session (or same-cutoff) days, excluding the day itself. A SHORTER window tracks recent regime changes faster and is noisier; a LONGER one is smoother and slower to react. The warm-up lookback scales with it automatically, so a wide window is never under-filled into an inflated ratio; the minimum-warm-days gate (20 prior sessions) does NOT scale down, so at the 30-row default a ticker needs 20 of its last 30 sessions populated before rvol is non-null. Omit for the standard 30-day baseline; pass 90 for the pre-2026-09 window."New value: +"Rolling RVOL baseline window, in trading rows (same-session days). Default 30; values outside 20-250 are clamped. This is the DENOMINATOR window: every RVOL in the response is that period's volume divided by the average of the trailing N same-session (or same-cutoff) days, excluding the day itself. A SHORTER window tracks recent regime changes faster and is noisier; a LONGER one is smoother and slower to react. The warm-up lookback scales with it automatically, so a wide window is never under-filled into an inflated ratio; the minimum-warm-days gate (20 prior sessions) does NOT scale down, so at the 30-row default a ticker needs 20 of its last 30 sessions populated before rvol is non-null. Unset means the standard 30-day baseline; 90 reproduces the pre-2026-09 window."
    • changedInput schema / properties / session / description
      Previous value: -"Restrict to one session bucket; omit to return all four sessions."New value: +"One session bucket; unset returns all four sessions."
  2. Addedv0.1.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds substantial context beyond them: the meaning of each baselineState value, why rvol can be null, the 20-prior-session warm-up gate that does not scale, and clamping of out-of-range baselineDays. It also warns that advRatio is not an RVOL and is not comparable to one, preventing a likely misinterpretation.

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 opening sentence front-loads purpose, session bucketing, and scope, and the rest is dense with substantive caveats rather than filler. It is a single long paragraph with some restatement of schema content (baselineDays warm-up mechanics), which slightly hurts scannability.

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?

For a 5-parameter analytical read with an output schema and annotations, the description covers the remaining interpretive gaps: baselineState semantics, null rvol explanation, advRatio/advDays meaning, and asOfTime's basis field. An agent can call this correctly without further documentation.

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%, so the baseline is 3, but the description adds meaning beyond the schema by spelling out the session bucket time windows (04:00-09:30, 09:30-16:00, 16:00-20:00) and how session='all' behaves, plus the denominator semantics of baselineDays. Some of this overlaps the already detailed schema text, so it stops short of 5.

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 ('Get the per-day relative-volume (RVOL) time series for a ticker') and defines the unit of return (per-day, per-session bucket with explicit ET windows). It does not name any sibling tool (e.g., get_volume_profile or get_premarket_scan_history) to differentiate itself, so it falls short of the top mark.

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 use case ('shows unusual premarket / session volume surges over the last N days') and explains the tradeoff for choosing a shorter vs longer baseline window. It offers no explicit when-not guidance or named alternative tools, which keeps it at 4 rather than 5.

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

Deploy Server

Other Tools