Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Dilution Instrument Rows by Family

get_dilution_instruments
Read-only

Retrieve one instrument family's dilution rows with per-field SEC citations. Request only families you need; unavailable means not measured, not zero.

Instructions

Get ONE instrument family's rows (10 credits) with per-field SEC citations — each figure carries the accession number, filing date and the verbatim quoted sentence it was read from, so every number can be traced to a filing. Families: warrants, convertibles, preferred, shelfs, atms, elocs, s1_offerings, equity_plans, exchangeables, recent_offerings. One family per call — request the families you actually need rather than sweeping all ten. 🔴 ROW-LEVEL WITHHOLDING: withheldRows / withheldRowCount mean specific rows could NOT be verified and were blanked, so every family total in the response is a LOWER BOUND, not a complete figure. Say so — presenting a holed total as complete understates a named issuer's dilution. An empty rows array on a covered company is a measured "none found in the filings read"; an unavailable response is not. ALWAYS RETURNS 200 — read available and reason, never the HTTP status. Coverage is partial: not_covered means THIS COMPANY HAS NOT BEEN ANALYSED YET, which is different from it having no dilution and different from an outage (an outage is a 5xx). Never report a company as having no dilution on the strength of an unavailable response. NULL, absent or withheld means NOT MEASURED — it NEVER means "no dilution", "no warrants", "no shelf" or zero. A numeric 0 is a MEASURED zero and defeats a null check, so decide from the accompanying availability/withheld/reason field, never from the value itself. If a figure is absent, say it was not measured; do not describe the company as having none of that instrument. Figures are as of meta.asOfDate, from filings read through meta.filingsThrough — a stale as-of date means the answer predates anything filed since, not that nothing has happened. Share counts are rebased onto a single split basis; a row that cannot be rebased is omitted and counted rather than published on a mixed basis. Included in Signal8 Pro — without it the call returns 403 with code FEATURE_NOT_AVAILABLE and requiredTier: "pro". That is a subscription-tier upgrade, not an add-on purchase; there is no separate add-on to buy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
familyYesInstrument family to return. One of: warrants, convertibles, preferred, shelfs, atms, elocs, s1_offerings, equity_plans, exchangeables, recent_offerings.
tickerYesStock ticker symbol (e.g., "MNTS", "VNRX")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description carries the full burden and exceeds it. It discloses credit cost, always-200 behavior, row-level withholding semantics, not_covered vs outage, null/zero interpretation, as-of date caveats, split rebasing, and tier-gated 403 behavior. This is far beyond annotation coverage and enables correct handling of ambiguous responses.

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?

Long but dense: every paragraph covers a distinct critical behavior (withholding, availability, null semantics, as-of, tier). Front-loaded with the core purpose and family list before caveats. Slight redundancy between 'Never report a company as having no dilution...' and the NULL/absent/withheld sentence, but overall well organized and justified by the tool's interpretation-sensitive response.

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?

Exceptionally complete for a read-only tool with 2 params and an output schema. The description covers credit cost, per-field traceability, withholding/lower-bound semantics, availability/reason fields, coverage vs outage, NULL interpretation, as-of date, split rebasing, and tier gating. An agent has everything needed to call the tool and interpret ambiguous responses 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?

Schema description coverage is 100%: both family and ticker are already described in the input schema, so baseline is 3. Description adds marginal meaning by noting 'one family per call' and reinforcing the family list, but does not materially enrich parameter semantics beyond the schema.

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 ONE instrument family's rows' with per-field SEC citations, and enumerates all ten families. This clearly distinguishes it from sibling dilution tools like get_dilution_snapshot or get_dilution_history, which focus on different aspects of dilution data.

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 clear context for use: 'One family per call — request the families you actually need rather than sweeping all ten.' It also explains the tier requirement (Signal8 Pro, 403 otherwise). However, it does not explicitly name alternatives or state when not to use this tool versus a sibling dilution tool.

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