Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Dilution Pressure Score and Risk Levels

get_dilution_risk
Read-only

Assess a company's dilution risk with a 0-100 pressure score, seven-component breakdown, and four risk levels. Understand score limitations via measured components and withheld reasons.

Instructions

Get the dilution pressure score (5 credits): a 0-100 score with its seven-component breakdown (shelf capacity, ATM/equity-line capacity, warrants in the money, convertible proximity, cash burn urgency, historical dilution, toxic financing), plus four risk levels β€” overall, offering ability, overhead supply, cash need. πŸ”΄ THE SCORE IS MEANINGLESS WITHOUT scoreMaxMeasured AND scoreWithheldReason: components whose inputs could not be measured are DROPPED FROM THE DENOMINATOR, so a score of 58 may be 58 out of 85, not out of 100. Always report it as score/scoreMaxMeasured and name the excluded components from scoreUnmeasuredComponents; NEVER rescale it to /100, and never treat a low numerator as a low-risk finding. A non-null scoreWithheldReason (e.g. unmeasured_score_components, unquantified_live_instruments, no_dilution_snapshot) means there is NO score β€” not a score of zero. πŸ”΄ WHEN levelsAreLowerBound IS TRUE THE LEVELS ARE FLOORS, NOT MEASUREMENTS: a "medium" then means AT LEAST medium, because instruments that could not be quantified were excluded from the sum. State it as a lower bound; presenting a floor as a measurement understates the risk of a named issuer. 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.2/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, explaining critical behaviors: the score denominator can shrink, levels are lower bounds, HTTP 200 is always returned, coverage gaps are not zero-risk, and null semantics. This is exceptional transparency for correct agent interpretation.

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 densely packed with critical warnings, front-loaded with the core output and key caveats. The emoji markers aid visual scanning, though a slightly tighter rewrite could reduce redundancy while keeping all necessary warnings.

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 complexity of the metric and the existence of an output schema, the description covers every ambiguity an agent might face: denominator handling, lower bounds, coverage gaps, null semantics, as-of dates, share rebasing, and tier gates. It is fully self-sufficient for correct use.

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 schema already fully describes the single required parameter with 100% coverage. The description adds no additional parameter-level details (e.g., ticker format is given in the schema), so the baseline of 3 applies without extra compensation needed.

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 specific verb ('Get') and resource ('dilution pressure score') with a 0-100 score, a seven-component breakdown, and four risk levels. This clearly differentiates it from siblings like get_dilution_snapshot or get_dilution_history by naming the exact metric produced.

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?

The description implies usage by defining the tool's output and includes a prerequisite (Signal8 Pro tier). However, it does not explicitly compare with sibling tools or state when to prefer this over get_dilution_snapshot or get_dilution_instruments, so guidance on alternatives is missing.

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