Signal8 MCP Server

Official

by signal8ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Stock Split History

get_split_history

Read-only

Retrieve a company's stock split history with dates, ratios, and type classification, including the cumulative 2-year reverse split ratio for NASDAQ/NYSE minimum bid-price compliance.

Instructions

Get stock split history for a company including forward and reverse splits with dates, ratios, type classification, and cumulative 2-year reverse split ratio. Relevant for NASDAQ/NYSE minimum bid-price compliance (1:250 cumulative reverse-split cap). IMPORTANT: cumulativeReverseSplitRatio2yr is null when it CANNOT BE STATED, which is NOT the same as no reverse splits — read cumulativeWithheldReason to tell them apart. unconfirmed_splits_in_window means at least one in-window reverse split is evidenced by only one source, so no cumulative is defensible: the confirmed splits alone would understate it, and understating a cumulative can put an issuer that breaches the 1:250 cap under it. Each row also carries confirmed; a confirmed: false split appears only in the announcement calendar, which retains every announcement and retracts none, so it is usually an amended or superseded announcement and occasionally a real split the effected-splits ledger missed. Both are returned. ratioDisplay and type are likewise null for a ratio whose exact factor cannot be determined.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ticker`	Yes	Stock ticker symbol (e.g., AAPL, TSLA)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description goes far beyond the readOnlyHint annotation by disclosing important null semantics, the distinction between null and no reverse splits, the handling of unconfirmed splits, and the retention of superseded announcements. This is rich behavioral context that an agent needs to interpret results correctly.

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 the core purpose and then provides substantial caveats that are necessary for correct interpretation. It is dense but not padded; however, the heavy block of caveats could be structured more clearly for an agent to parse quickly.

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 single-parameter, read-only tool with an output schema available, the description is complete enough. It covers the returned split types, null conditions, annotation-calendar behavior, and the compliance context, so an agent has sufficient guidance to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema fully describes the only parameter, ticker, with 100% coverage, so the description does not need to add parameter-level detail. The baseline of 3 is appropriate because the description adds no extra semantics for the input parameter itself, though this is acceptable given the schema completeness.

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 opens with a specific verb and resource: 'Get stock split history for a company,' and enumerates concrete contents (dates, ratios, type classification, cumulative ratio). It is inherently distinct from sibling tools like get_upcoming_reverse_splits, which target future events rather than historical records.

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 context for when this tool is relevant: NASDAQ/NYSE minimum bid-price compliance and the 1:250 cumulative reverse-split cap. It does not explicitly name alternatives or state when not to use it, but the 'history' framing plus sibling names makes the intended use reasonably obvious.

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

Deploy Server