Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

IPO Risk Factors (classified risk factors from an IPO prospectus)

sections_ipo_risk_factors
Read-onlyIdempotent

Classified risk factors from a company's IPO prospectus — prefers the 424B4 (final pricing prospectus), falls back to S-1 / S-1A if no 424B4 exists for the CIK in the corpus. Mirrors sections__risk_profile but on the PRE-IPO filing, so it works for names that just went public (or are about to price) and have no 10-K yet.

Returns a thematic + topic breakdown (counts per risk category) plus the individual risk factors (heading + primary_label + topics + verbatim text snippet). Pair with sections__ipo_screen — screen recent IPOs, then pull each one's risk-factor profile.

Perf caveat: risk-factor labels are precomputed (<100ms) for most filings. For 424B4s upserted before the 2026-07-21 labeler fix, the callable runs the labeler at query time (provenance.labels_source='runtime_fallback') — ~18s on the first such call (labeler warm-up), ~2-3s per new filer after.

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

Input Schema

NameRequiredDescriptionDefault
yearNoOptional: year of the 424B4 to use (disambiguates multiple).
accessionNoOptional: pin a specific filing accession number.
top_n_topicsNoHow many top topics to include in the summary breakdown (default 10).
ticker_or_cikYesCompany ticker, digit-string CIK, or integer CIK. Required.
max_chars_per_factorNoTruncate each risk-factor text snippet to this many chars (default 400).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/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: the filing-selection fallback order, the return payload shape (counts per category plus heading/label/topics/snippet), and a precise performance caveat including the ~18s cold-call cost and the provenance.labels_source='runtime_fallback' signal. That latency disclosure is exactly the kind of thing an agent needs to plan around and is not derivable from annotations.

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 returns, then workflow pairing, then the perf caveat — a sensible ordering with little waste. The perf paragraph is long and dash-heavy, but each clause (warm-up vs per-filer timing, provenance flag) carries operational value, so it earns most of its length.

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?

No output schema exists, and the description compensates fully by enumerating the return structure (category counts plus per-factor heading, primary_label, topics, verbatim snippet). Combined with the fallback and latency notes, an agent has everything needed to call this correctly and interpret the result.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: 'year' is framed as disambiguating among multiple 424B4s, 'accession' as pinning a specific filing, and the thematic/topic breakdown explains what top_n_topics governs. This lets an agent reason about parameter selection rather than just reading types.

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 (extract classified risk factors from an IPO prospectus) and nails the scope with the filing-preference rule (424B4 first, S-1/S-1A fallback). It explicitly distinguishes itself from sections__risk_profile by noting it operates on the PRE-IPO filing, so an agent can route without opening either 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 an explicit when-to-use condition ('works for names that just went public... and have no 10-K yet') and a concrete workflow with the sibling ('Pair with sections__ipo_screen — screen recent IPOs, then pull each one's risk-factor profile'). The alternative-behavior exclusion is handled by naming the fallback chain rather than leaving the agent to guess which filing gets used.

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