Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Upcoming Reverse Splits

get_upcoming_reverse_splits
Read-only

Find upcoming reverse stock splits for small-cap companies within a specified date window. Returns ticker, ratio, effective date, market cap, and float for each scheduled split.

Instructions

Get reverse stock splits SCHEDULED to take effect within a day-offset window of the current US market day, for companies under a market-cap ceiling. Offsets are days from today on the US market calendar: fromOffset=1, toOffset=1 is tomorrow; fromOffset=1, toOffset=7 is the week ahead. Each row carries the ticker, company name, the exact vendor integers (splitFrom/splitTo), a pre-rendered ratio ("1-for-20"), the effective date, market cap, float in SHARES, and price. WHAT THIS IS: rows are splits scheduled AS OF NOW — not a guarantee that every split effective in the window is already known. The underlying stock_splits table has NO created_at column, so there is no way to measure when a row first appeared, and a split announced later will simply be missing. Describe results as "scheduled as of now", NEVER as "all of" or "every" reverse split. A scheduled split can also be postponed or cancelled after it is announced. 🔴 capUnknownCount IS A WITHHOLDING COUNT, NOT A ZERO. It counts rows that passed every other filter and were DELIBERATELY EXCLUDED because Signal8 has no measured market cap for them — typically real OTC microcaps. It does NOT mean those companies have no dilution, no split, or no cap; it means the cap was not measured, so they cannot be asserted to sit under the stated ceiling. If you publish a "under $Xm" framing and capUnknownCount is above zero, say that N further companies were withheld for unmeasured market cap — do not present the list as complete and do not describe the withheld rows at all. Funds, ETFs and sub-1.5x fractional ratio adjustments are already removed server-side; do not re-filter or re-derive the ratio. AN EMPTY splits ARRAY IS A NORMAL, COMMON RESULT — most single weekdays have no sub-cap reverse split scheduled at all. It is NOT an error, NOT a failure, and NOT evidence that reverse-split activity has stopped. Publish nothing rather than publishing an empty-list framing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toOffsetNoWindow end, inclusive, as a day offset from the US market day (default 1). Use 7 with fromOffset 1 for the week ahead.
fromOffsetNoWindow start as a day offset from the US market day (default 1 = tomorrow). Must be <= toOffset; an inverted window is rejected rather than silently returning an empty list.
maxMarketCapNoExclusive market-cap ceiling in USD (default 300000000). Rows with NO measured market cap are excluded and counted in capUnknownCount, never assumed to be under the ceiling.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

Even though readOnlyHint=true is annotated, the description adds substantial behavioral context: the source table has 'NO created_at', rows are not a guarantee, capUnknownCount is a 'WITHHOLDING COUNT, NOT A ZERO', and an empty array is a 'NORMAL, COMMON RESULT'. This goes far beyond the annotations without contradicting them.

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 front-loaded with a clear one-sentence purpose and uses headings/caps to organize warnings. It is long, but most length is justified by the tool's tricky semantics; a few points are restated for emphasis, preventing a perfect score.

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 an output schema present, return-value details need not be re-explained. The description covers edge cases thoroughly: scheduling uncertainty, capUnknownCount meaning, server-side filtering, empty-array normality, and required output phrasing. Nothing an agent needs to invoke and interpret the tool 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 100%, so the baseline is 3. The description adds value beyond the schema by explaining offset semantics with examples like 'fromOffset=1, toOffset=1 is tomorrow' and clarifying how capUnknownCount relates to maxMarketCap exclusions.

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: 'Get reverse stock splits SCHEDULED to take effect within a day-offset window... under a market-cap ceiling.' The scope is unambiguous and the focus on scheduled reverse splits distinguishes it from historical or dilution-related siblings.

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?

Provides strong usage context and explicit guardrails, such as 'Describe results as "scheduled as of now", NEVER as "all of" or "every"' and 'do not re-filter or re-derive the ratio.' It does not name an alternative tool, but the when/how guidance is clear.

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