Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Baby-Shelf (S-3 I.B.6) Raisable Capacity

get_baby_shelf_capacity
Read-only

Calculates remaining SEC Form S-3 I.B.6 "baby shelf" capacity using public float and trailing 12-month takedowns, returning the cap, counted sales and raisable amount.

Instructions

SEC Form S-3 General Instruction I.B.6 "baby shelf" capacity: how much the issuer may raise off an effective shelf now, under the one-third-of-public-float cap that applies below a $75M non-affiliate float, less trailing-twelve-month takedowns. Returns the float basis, the cap, takedowns counted and the remaining raisable amount. constraintApplies: false: the cap does not bind (float >= $75M, primary offerings unlimited under I.B.1); this is neither "no capacity" nor a favourable finding. constraintApplies: null with suppressedReason: "float_unmeasured": the float value was not measured, so whether the cap binds is unknown; it does not mean the cap does not bind and does not mean unlimited. A suppressed figure is withheld (e.g. an issuer delisted to OTC cannot run an S-3 primary): the capacity is not stateable, which is not $0 raisable. suppressedReason: "ib6_pool_unattributed": the cap applies but trailing sales could not all be attributed, so $0 is a lower bound; remainingCapacity is null and capacity lies between capacityLowerBoundDollars and capacityUpperBoundDollars (at most the upper bound). remainingCapacityBasis: "lower_bound": the figure counts unattributed rows whole, so capacity is at least remainingCapacity and at most capacityUpperBoundDollars. staleIssuerStatement: the issuer's own $0 statement dated asOf was not used because sales its window counted have since left today's window; it is what the issuer stated as of that date, not today's capacity. poolDerivations: ATM periods split by differencing the issuer's own stated sub-periods, each with its accession. suppressedReason: "issuer_not_ib6_limited": the issuer's current prospectus offers more than the cap with no I.B.6 limitation (issuerUnlimitedOffer); whether the cap applies is not measured, and is neither $0, constrained nor unlimited. floatValueBasis: "issuer_stated": the issuer's own printed I.B.6 float (issuerStatedFloat, prospectus <= 60 days old) was lower than the live valuation and was used. A null remaining capacity is not measured, not zero. Returns HTTP 200 for unavailable data; the available and reason fields say why. not_covered means this company has not been analysed yet, not that it has no dilution; an outage is a 5xx. A null, absent or withheld value means the figure was not measured; it does not mean "no dilution", "no warrants", "no shelf" or zero. A numeric 0 is a measured zero, so availability is carried by the availability, withheld and reason fields, not by the value. Figures are as of meta.asOfDate, from filings read through meta.filingsThrough (a stale date predates anything filed since). Share counts are on one 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 FEATURE_NOT_AVAILABLE with requiredTier: "pro" (a tier upgrade; there is no add-on to buy).

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

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., "MNTS", "VNRX")

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, and the description adds substantial context beyond that: a Pro tier gate returning 403 FEATURE_NOT_AVAILABLE with requiredTier 'pro', HTTP 200 for unavailable data versus 5xx for outages, not_covered meaning 'not yet analysed', and staleness via meta.asOfDate and meta.filingsThrough. The dense suppressedReason taxonomy (float_unmeasured, ib6_pool_unattributed, issuer_not_ib6_limited) further discloses exactly why a figure can be withheld rather than zero. It stops short of describing output field shapes beyond names, but the output schema covers that.

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 purpose is front-loaded in the first sentence, and most edge-case clauses add real interpretive value. However, the passage is roughly 450 words of uninterrupted prose with repeated restatements that null/absent means 'not measured, not zero' (once in the capacity discussion, again in the general availability paragraph), plus a stock boilerplate line about 'no dilution', 'no warrants' and 'no shelf' that is tangential to this tool.

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?

For a single-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs to call it and to avoid misreading the result: availability semantics, tier gating, staleness bounds, split-basis omissions, and the meaning of every suppression state. Nothing material is missing.

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 only one parameter (ticker) with 100% schema coverage including an example, so the schema already carries the semantics. The description adds nothing about ticker format, exchange suffixes, or behavior on unknown symbols, making the baseline 3 appropriate.

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 up front: computes S-3 General Instruction I.B.6 'baby shelf' capacity — how much the issuer may raise off an effective shelf now, under the one-third-of-public-float cap, less TTM takedowns. It also enumerates what comes back (float basis, cap, takedowns counted, remaining amount), which clearly separates it from float-only siblings such as get_float or get_float_history.

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 implied by the domain framing, but the description never names an alternative tool (get_float, get_dilution_snapshot, get_dilution_risk) or states when to pick this one over them. What it does provide is extensive guidance on how to read edge-case results, which helps post-call interpretation more than tool selection.

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