Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

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

get_baby_shelf_capacity
Read-only

Determine remaining capacity under the SEC's baby shelf rule based on public float and trailing takedowns. Returns cap, takedowns counted, and raisable amount, or explains why it's not measurable.

Instructions

Get the SEC Form S-3 General Instruction I.B.6 "baby shelf" capacity (10 credits): how much the issuer may raise off an effective shelf right now, given the one-third-of-public-float cap that applies below a $75M non-affiliate float, less the trailing-twelve-month takedowns already used. Returns the public float basis, the cap, takedowns counted and the remaining raisable amount. 🔴 constraintApplies: false means the cap does NOT bind (float at or above $75M, so primary offerings are unlimited under I.B.1) — it is NOT "no capacity" and NOT a favourable finding. 🔴 A suppressed response means the figure is WITHHELD (for example an issuer that has been delisted to OTC and cannot run an S-3 primary at all) — report it as not stateable, NEVER as $0 raisable, which is a claim. A null remaining capacity is likewise not measured, not zero. 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.3/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. It discloses critical behavioral traits: always returns 200 regardless of success, must read internal fields not HTTP status, partial coverage and what not_covered means, null/absent meaning not measured, 0 being measured, as-of date semantics, share rebasing, and the 403 feature-tier behavior. This is exactly the kind of side-effect/interpretive info an agent needs, and it is consistent with annotations.

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 very long and contains some redundancy, e.g., 'NULL, absent or withheld means NOT MEASURED' is repeated several times with slightly different phrasings. It is front-loaded with the purpose, but the many caveats, while valuable, could be tightened. It is not minimal, though every major sentence adds unique guidance.

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 complex regulatory calculation tool with many edge cases, the description is exceptionally complete. It covers interpretation of every non-obvious response state (constraintApplies false, suppressed, not_covered, null, 0, stale as-of, rebasing, 403) and explicitly warns against common misreporting. The output schema exists, so return-structure details are not needed here.

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 documents the single 'ticker' parameter (100% coverage). The description does not add any additional meaning about the parameter itself, so the baseline of 3 applies. It doesn't hurt or help 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?

The description states a specific verb ('Get') and resource ('SEC Form S-3 General Instruction I.B.6 baby shelf capacity') and explains exactly what the tool computes (raisable amount under the one-third cap, given public float and takedowns). It also lists the returned fields. This clearly distinguishes it from the many sibling get_* tools by naming a unique regulatory concept.

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?

The description provides clear context on when the cap applies or not (float below/above $75M), how to interpret suppressed/null/not_covered outcomes, and when the tool returns 403. It does not explicitly mention alternative tools or say 'use this instead of X', but the subject matter is so specific that implicit usage is strong. Since there is no explicit exclusion of siblings, it stays at 4 rather than 5.

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