Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Reverse Split Lifecycle

get_reverse_split_lifecycle
Read-only

Retrieve a company's SEC-filing-tracked reverse-split lifecycle, including episode states, ratios, key dates, approval paths, and verbatim source quotes for due diligence.

Instructions

The reverse-split lifecycle Signal8 has tracked from a company's own SEC filings (proxies, 8-K Items 3.03/5.03/5.07, 6-Ks): one episode per split authority, newest first, each with its state (proposed, vote scheduled, approved, ratio set, effective date announced, charter filed, ... or closed), the ratio or authorised range, meeting / vote / effective dates, the state history, and the events behind it oldest first. Every event carries its source (accession and an EDGAR sourceUrl) and its facts; every stated fact carries the verbatim quote it was read from. Not stated means not measured, not "no": a fact with notStated:true (or a null field) means the documents read did not say it, not that it is false, zero or absent. coverage "unresolved" means the ticker could not be matched to an SEC registrant (not measured). coverage "tracked" with an empty episodes list means no episode has been tracked from the filings read since the tracker started; it is not evidence that no reverse split is planned. effectiveDate is the date the issuer stated, strictly parsed: a scheduled date, not a confirmation that the split happened (it can be postponed or abandoned). A conditional date ("the 25th trading day after the Trigger Event") is returned verbatim in effectiveCondition and is not a date; no date is computed from it. verification is copied from the tracker: "provisional" = one source, not cross-checked (the default, not "doubtful"); "verified" = cross-checked. Approval (present only when approvalAvailable is true): each episode carries approvalPath {path, label, quote, sourceUrl}: shareholder_vote, written_consent, fpi_written_resolution, pre_approved_range (the board set the ratio inside a range shareholders approved earlier), board_only (the company's own filing states no shareholder approval was required, quoted), depositary_ratio_change (an ADS ratio change by the depositary, no shareholder vote, the ordinary shares not consolidated) or unknown. The response also carries domicile {code, label, group, source} (EDGAR, else the latest 10-K / 20-F cover; null = not measured, not "Delaware") and splitAuthority {authority, basis, label, boardMayActWithoutVote, conditions, statute, quote, sourceUrl}. Only basis own_prior_board_only_announcement or charter_clause is board split authority on file: a charter clause is a standing power; own prior evidence is a PAST board-only split (dated in the label, conditional on its statute, e.g. NRS 78.207 needs authorized shares cut by the same ratio), not a power to skip a vote now, and the current split can still go to a vote. authority "unknown" or basis "domicile_default_only" is not a finding about the company: it only states what the domicile's law allows by default (e.g. "Domicile may permit board action; charter not checked"), not that this company can split without a vote. vote_required appears only as a labelled domicile default, not as a statement that a vote is needed. path "unknown" is not "no vote"; a missing proxy does not determine a path. An HTTP 503 FEATURE_DISABLED means the lifecycle tracker is switched off and the response says nothing about the company's splits.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesUS stock ticker, e.g. "ABCD" or "BRK.B".

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0

TDQS

A3.7/5.0
Behavior5/5

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

Annotations only declare a safe read; the description adds substantial context beyond them: per-event source accession and EDGAR URL, verbatim quotes backing each fact, the notStated/null semantics, verification 'provisional' vs 'verified', the 503 FEATURE_DISABLED switch-off case, and the warning that effectiveDate is an issuer-stated schedule not a confirmation. The long list of explicit non-inferences ('unknown' is not 'no vote', domicile_default_only is not a finding, empty episodes is not evidence of no split) is exactly the anti-misreading guidance an agent needs on this data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single, very long, unparagraphed block of dense prose with nested enumerations of approvalPath values, splitAuthority bases and coverage semantics. Much of that enumerates return structure even though an output schema exists, and the caveats are interleaved rather than grouped, so the load-bearing parts (what the tool returns, and the notStated warning) are hard to extract on a fast read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a semantic, evidence-backed data tool with one simple input, the description covers the important traps: unmeasured vs false, conditional dates, provisional verification, board-authority limits and the disabled-feature error. Since an output schema exists, the surplus return-field detail is not required, and the only real omission is guidance on which reverse-split sibling to prefer.

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?

There is a single parameter, 'ticker', and the schema already documents it at 100% coverage including the 'BRK.B' example. The description adds no further meaning about the ticker (no fallback for unmatched tickers beyond the coverage 'unresolved' note), so the baseline of 3 applies.

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?

The opening clause states a specific verb and resource: the reverse-split lifecycle tracked from SEC filings, one episode per split authority, newest first, with state, ratio, dates, history and events. That is far more specific than the title restated. It never names the adjacent siblings (get_reverse_split_authority, get_upcoming_reverse_splits, get_ended_reverse_splits, get_split_history), so differentiation from them is left to the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool is for tracking an episode end-to-end, and the description explains what empty or 'unresolved' results mean, which helps the agent interpret a call. But there is no explicit 'use this when you need X instead of Y' and no named alternative among the many reverse-split siblings, so selection between them is inference.

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