Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

IPO Financials (per-period financial statements from the IPO prospectus)

sections_ipo_financials
Read-onlyIdempotent

Per-period financial statements extracted from a company's IPO prospectus — the revenue / operating-income / net-income / cash / balance-sheet time series from the 424B4, ordered oldest→newest. Fills the 'no 10-K history yet' gap for a company that JUST went public (or is about to price) and has no post-IPO annual filing.

financials[] — one row per reported period (annual / interim) with period / period_type / period_end + ~13 financial fields (revenue, operating_income, net_income, cash_and_equivalents, …). NULLs are preserved (a field the prospectus didn't report stays null — not zero).

status ∈ ok / no_financials_extracted (IPO in universe but no financials pulled) / not_in_universe (not a catalyst-window IPO).

Input: ticker_or_cik (CIK preferred). Pairs with sections__ipo_offering (deal terms + lockup), sections__ipo_risk_factors (risk factors), and sections__ipo_screen (find the IPO). Note: de-SPAC filers may currently return the pre-merger financials until the shared SPAC-aware resolver is applied here (sections follow-on).

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_or_cik": "<ticker_or_cik>"
    },
    "name": "sections_ipo_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticker_or_cikYesIssuer CIK (digit string or int — preferred) or ticker (resolved to its CIK). Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, but the description adds substantial behavior beyond them: NULLs are preserved rather than zeroed, results are ordered oldest→newest, the three status outcomes are defined (ok / no_financials_extracted / not_in_universe) with the meaning of each, and a known de-SPAC resolver caveat is disclosed. That is exactly the kind of caveat and edge-case disclosure structured fields cannot carry.

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 the one-sentence purpose before the field/status detail, and the sibling references are packed compactly into a single clause. It is dense and uses abbreviations ('424B4', 'de-SPAC') and a truncated field list, but every block (rows, statuses, input, siblings, caveat) carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description must carry return-shape information — and it does: the financials[] row structure with period/period_type/period_end plus ~13 named fields, NULL semantics, and the enumerated status values. Combined with the single documented input, an agent has everything needed to call and interpret this tool.

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?

With a single parameter at 100% schema description coverage, the schema already documents the CIK-preferred-versus-ticker resolution rule. The description's 'Input: ticker_or_cik (CIK preferred)' restates that rather than adding new semantics, so the baseline of 3 applies.

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 ('Per-period financial statements extracted from a company's IPO prospectus'), names the source document (424B4), specifies ordering (oldest→newest), and distinguishes itself from 10-K-based financial data by naming the exact gap it fills. An agent can identify this tool's scope without opening the schema.

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?

Explicit routing context: use it for a company that just went public or is about to price and has no post-IPO annual filing, plus named companions (ipo_offering for deal terms/lockup, ipo_risk_factors, ipo_screen to find the IPO). It stops short of naming the alternative financials tool to use when 10-K history does exist, leaving that inference to the agent.

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