Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Reverse Split Authority

get_reverse_split_authority
Read-only

Find companies whose boards can still execute reverse splits under existing approval without a new shareholder vote, showing approval status, stated expiry, and remaining split room.

Instructions

Companies whose board still holds reverse-split authority it may use without another shareholder vote: an approval on file (shareholder vote or written consent; tracker states consent_pending, voted_approved, ratio_fixed) not past a stated expiry, one row per company (its newest approval; other live ones in otherLiveAuthorityEpisodeIds). Soonest stated expiry first. Each row is the Reverse Splits page row (ticker, companyName, ratio, exchange, approvalPath, domicile, splitAuthority, authorityTerms, sourceUrl / sourceAccession, sourceDocuments: every document behind the approval with accession or URL) plus an "authority" block: episodeId, state, approvedDate, approvedRatio {fixed, min, max} (the per-split ratio or range approved), cumulativeCap (cap on the product of every split drawn on it), multiStep, expiresOn, expiryTerm, daysUntilExpiry, and room: capRatio + capBasis ("cumulative_cap", or "single_split_maximum" = no cumulative cap stated and nothing drawn, so one split up to the approved maximum), perSplitMax, usedSplits + usedRatio (product of the splits already executed on it; 1 = none drawn), remainingRatio (capRatio / usedRatio), exhausted, nextSplitMax, pendingRatio (a ratio the board set that has not taken effect) and a one-line label. The approval route is approvalPath.path (shareholder_vote, written_consent, fpi_written_resolution, pre_approved_range, board_only, depositary_ratio_change or unknown = "Not determined", not "no vote"). Ratios are 1-for-N factors and combine by product. Not measured is not "none remaining": room.remainingRatio null comes with room.notMeasuredReason ("cumulative_cap_not_stated", "ratio_not_stated" or "drawn_split_ratio_not_stated"), meaning the remaining room is not measured for that reason. Such rows are listed, never dropped, and are not full. expiresOn null = the documents read state no expiry, not "never expires". An empty list is what the tracker has on file, not evidence that no board holds authority. This screen covers approvals on file; a board that may split under its statute or charter with no approval at all shows as splitAuthority.boardMayActWithoutVote on a row and in the per-company lifecycle, and is not listed here on that basis alone. Locked rows are withheld, not absent. The facts are part of Signal8 Pro: a key not owned by a Pro account gets rows with locked: true and only ticker, companyName, hasPage and exchange (access "preview", lockedCount). minRemaining and expiringBefore are Pro-only filters (on a non-Pro key they apply to unlocked rows only; filtersLimitedToUnlocked: true). A row whose remaining room or expiry is not measured never matches those filters; excludedNotMeasured counts how many were left out for that reason. Paging uses limit and nextCursor. available: false or an HTTP 503 FEATURE_DISABLED = unavailable, and the response says nothing about any company. The data describes what is on file and carries no view on whether a split will happen, what it means for the price, or what anyone should do.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_reverse_split_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, 1 to 200 (default 50).
cursorNonextCursor from the previous page. Omit for the first page.
exchangeNoListing venues to keep: NASDAQ, NYSE, AMEX (NYSE American), OTC, or not_measured. Empty = every row.
minRemainingNoKeep rows whose room.remainingRatio is at least this N (1-for-N), e.g. 50. Rows not measured never match.
expiringBeforeNoKeep rows whose stated expiresOn is before this YYYY-MM-DD day. Rows with no stated expiry never match.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses substantial behavior: locked rows are withheld, non-Pro keys receive preview rows with only a few fields, Pro-only filters apply differently to unlocked rows, unavailable/503 responses carry no company information, and not-measured values must not be treated as zero remaining room. It also explains the meaning of null expiry and empty results, which are important behavioral caveats for an agent.

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

Conciseness3/5

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

The description is front-loaded with the core purpose, but it is extremely long and delivered as one dense paragraph. Much of the length is justified by complex access, measurement, and row-shape details, yet the lack of structural breaks makes it harder to scan than necessary.

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?

Given the tool's complexity, five optional parameters, output schema, and access-tier behavior, the description is highly complete. It covers row shape, authority fields, ratio-combining rules, not-measured semantics, locked preview behavior, paging, filter limitations, and unavailable responses. An agent has enough context to invoke the tool correctly and interpret its edge cases.

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 description coverage is already 100%, so the schema carries baseline parameter meaning. The description adds important semantics beyond the schema by noting that minRemaining and expiringBefore are Pro-only filters, that rows lacking measured room or expiry never match them, and that excludedNotMeasured reports those exclusions. It does not add much beyond the schema for cursor or exchange, but the access and filter-exclusion context is meaningful.

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 states a precise resource and scope: companies whose boards still hold reverse-split authority usable without another shareholder vote, with one row per company and its newest approval. This clearly distinguishes the tool from sibling reverse-split screens that cover actual splits, upcoming splits, ended splits, or lifecycle events.

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?

It explains when this screen applies versus actual split lists: approvals on file are listed here, while a board that may act under statute or charter without an approval appears in the per-company lifecycle instead. It also clarifies filter behavior for not-measured rows and empty-list semantics. It does not explicitly name the other reverse-split siblings as alternatives, so it falls short of full when-to-use routing.

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