Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Dilution Snapshot Summary

get_dilution_snapshot
Read-only

Check a ticker's dilution risk with summary totals, cash position, float block, and data provenance in one snapshot. Use coverage status first to avoid charges for unanalysed companies.

Instructions

Get the dilution snapshot header (25 credits — the most expensive tool here): summary totals (potential new shares and their percentage of shares outstanding, per-family share totals), the cash position (anchor cash, monthly burn, estimated current cash, runway months), the float block, and meta provenance. DOES NOT INCLUDE INSTRUMENT ROWS — call get_dilution_instruments per family for those, and call get_dilution_coverage first to avoid paying 25 credits for an uncovered ticker. 🔴 FLOAT: when floatWithheldReason is non-null the tradeable float was NOT MEASURED and must not be stated as a number. tradeableFloatCeiling is an UPPER BOUND ("at most X"), NOT a float — never feed it to a market capitalisation, a percent-of-float, a short-interest ratio or a comparison; render it with a ≤ and say it is a bound. 🔴 RUNWAY: a runway figure beside goingConcern: true is a contradiction the issuer's own auditors have flagged — report both, never the runway alone. 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
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
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses critical behavioral traits: 25-credit cost, always-check-available/reason semantics, null-versus-zero meaning, rebasing of share counts, and the float/runway interpretive traps. However, it says 'ALWAYS RETURNS 200' and then later says the call returns 403 without Pro, which is an internal inconsistency that slightly undermines the transparency.

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 long but well organized, front-loading the purpose and cost and then grouping key warnings by topic with clear markers. Some redundancy exists, such as the repeated add-on purchase clarification, but every major caveat earns its place for a costly tool with many traps.

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?

Despite having an output schema, the description goes beyond it by covering authorization, cost, coverage semantics, missing-data interpretation, as-of date staleness, split rebasing, and the float/runway misuse risks. For a tool with this many edge cases, the definition is effectively complete.

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 has one required parameter, ticker, with a complete description of what it is. The tool description adds contextual warnings about covered vs. uncovered tickers but no additional parameter syntax or formatting details, so it stays at the baseline expected for full schema coverage.

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 names a specific verb and resource: it gets the dilution snapshot header/summary, and it explicitly says what is excluded (instrument rows), which cleanly separates it from get_dilution_instruments and get_dilution_coverage. The scope, contents, and caveats are all clear.

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

Usage Guidelines5/5

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

The description gives explicit routing guidance: call get_dilution_coverage first to avoid paying 25 credits for an uncovered ticker, and call get_dilution_instruments per family because instrument rows are not included. It also explains the 403/Pro-tier condition and covers the not_covered vs. outage distinction, so an agent knows when to use this tool and when not to.

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