Skip to main content
Glama

KeyVex

get_registration_statements

Read-only

Returns SEC Form S-1 / S-3 / S-3ASR registration statements — securities offering registrations filed with the SEC. Use this when the user asks about: which companies are going public (IPO pipeline via S-1), shelf registrations (S-3 / S-3ASR — company registers securities to sell over multiple offerings without re-registering; large established issuers use the automatic S-3ASR variant), recent secondary offerings, registration amendments updating prior filings, or to bridge from a company name / ticker to the prospectus prose. Forms covered: S-1 — Initial registration (IPO + first-time registrants) S-1/A — Amendment to an S-1 S-3 — Shelf registration (issuers meeting reporting / market-cap criteria; lets them issue securities over time without re-registering each time) S-3/A — Amendment to an S-3 S-3ASR — Automatic shelf registration. The shelf form used by Well-Known Seasoned Issuers (large established companies like Apple, Ford, most of the S&P 500). Effective on filing. These issuers file S-3ASR, NOT plain S-3. Source: SEC EDGAR full-text search. Returns one record per filing, deduped by accession. Exhibit attachments (EX-10, opinion letters, fee tables, etc.) are filtered out — only the canonical form types are returned. v1A is metadata only. Each record has filer name + CIK + optional ticker + SEC file_number, state, SIC code(s), and URLs. Substantive prospectus content (offering size, share counts, use of proceeds, risk factors, financial statements) lives at primary_document_url — agents follow for the prose. SCOPE — covers S-1 (IPO), S-3 + S-3ASR (shelf, including WKSI auto shelves), plus /A amendments. S-8 employee-benefit-plan registrations, S-4 merger/acquisition registrations, and F-series foreign-issuer forms are NOT ingested. 424B prospectus supplements (offering takedowns off an existing shelf) are out of scope — query the shelf registration itself. Amendment chains: all amendments share the same sec_file_number as the original. Use sec_file_number filter to fetch an entire amendment chain. Pure-publisher posture: KeyVex doesn't derive 'likely-to-IPO' or 'price-target' signals from registration filings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum filings to return. Default 50, max 500.
sinceNofile_date lower bound (YYYY-MM-DD inclusive).
untilNofile_date upper bound (YYYY-MM-DD inclusive).
s1_onlyNoWhen true, restricts to S-1 family (S-1 + S-1/A) — the IPO / first-time pool.
s3_onlyNoWhen true, restricts to S-3 family (S-3 + S-3/A + S-3ASR) — the shelf pool, including automatic shelf registrations filed by Well-Known Seasoned Issuers.
filer_cikNoFiler's SEC CIK (1-10 digits).
filing_idNoEDGAR accession number. Direct doc lookup.
filer_nameNoCase-insensitive substring against the filer's entity name (e.g., 'kraneshares', 'karyopharm'). NOTE: matched over a recent-filing window, so it reliably finds CURRENT filers but can miss an issuer whose registrations are older than that window. To pull a specific issuer's full registration history regardless of date, use filer_cik (most reliable) — e.g. Circle Internet Group is filer_cik 0001876042.
sort_orderNoDefault: desc (most recently filed first).
filing_typeNoExact filing-type match.
filer_tickerNoTicker symbol (e.g., 'KPTI'). Often empty for IPO-stage S-1 filers (they don't have a ticker yet).
sec_file_numberNoSEC-assigned registration file number ('333-XXXXXX'). Stable across amendments — use to fetch a full amendment chain.
exclude_amendmentsNoWhen true, drops /A amendments. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/destructive=false, and the description adds substantial context beyond that: records are metadata-only in v1A, deduped by accession, exhibit attachments (EX-10, opinion letters, fee tables) are filtered out, substantive content lives at primary_document_url, and the publisher does not derive IPO-likelihood or price-target signals. That is real behavioral disclosure, not restatement.

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?

Front-loaded with purpose, then triggers, then scope — a good ordering. It is long, but 13 parameters and a five-form taxonomy justify much of the length; the per-form glossary is somewhat verbose and partially duplicates the filing_type enum descriptions, which costs a point.

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?

With no output schema, the description carries the return-shape burden and does: one record per filing, deduped, filer name + CIK + optional ticker + file_number, state, SIC codes, and URLs, with primary_document_url as the follow-on target. Scope, taxonomy, and amendment behavior are all covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by explaining cross-parameter semantics: amendments share one sec_file_number so that filter retrieves a full chain, and it repeats the filer_name recent-window caveat with filer_cik as the reliable fallback. Some of this overlaps the schema text, but the amendment-chain workflow adds genuine meaning.

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+resource (SEC Form S-1/S-3/S-3ASR registration statements) and immediately narrows it with explicit boundaries: S-8, S-4, F-series are NOT ingested and 424B supplements are out of scope. An agent can distinguish this from get_private_placements, get_reg_a_offerings, get_proxy_filings, and get_sec_comment_letters without opening a schema.

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?

Gives explicit user-intent triggers ('which companies are going public', 'shelf registrations', 'bridge from a ticker to the prospectus prose') and explicit exclusions (S-8/S-4/F-series, 424B takedowns — query the shelf itself). It also routes the agent to sec_file_number for amendment chains, which is an alternative-path instruction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources