Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

IPO Offering Card (deal terms + lockup per issuer, 424B4 + catalyst)

sections_ipo_offering
Read-onlyIdempotent

One structured IPO offering + lockup card per issuer — the deal terms extracted from the 424B4 prospectus, JOINed to the catalyst lockup schedule. Covers 98.3% of the catalyst IPO universe (2,522 issuers).

offering: price_low/high, shares_offered, greenshoe_shares, exchange, ticker, deal_size_full, underwriters[], share_classes[], dual_class_flag, net_proceeds, use_of_proceeds[]. lockup: lockup_days, lockup_expiry, shares_locked, locked_pct_of_total, early_release_trigger, holder_types, tranche, is_confirmed. Plus per-source provenance (offering vs lockup source + extraction timestamp).

status ∈ ok (full card) / lockup_only (in catalyst but offering not extracted) / not_in_universe (not a catalyst-window IPO — e.g. a company that IPO'd long ago).

Input: ticker_or_cik (CIK preferred — digit string or int resolves directly; a ticker is resolved to its CIK). Pairs with sections__ipo_screen (find the IPO) and sections__ipo_risk_factors (its risk factors).

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

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.2/5.0
Behavior4/5

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

With readOnlyHint/idempotentHint already covering the safety profile, the description adds substantive behavior: which fields come from which source, per-source provenance and extraction timestamps, and the three-way status outcome that explains partial or empty results. The one gap is that it does not state how absent subsections render (nulls vs omitted) in the lockup_only case, but the coverage figure and status semantics go well beyond the 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 a one-sentence definition of what the card is, then grouped field lists under 'offering:' and 'lockup:', then status semantics, then input and pairings. The field enumeration is long but earns its place given there is no output schema. Minor redundancy between the input sentence and the parameter schema wording.

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 full burden of describing the return value and does so field by field, plus provenance and status codes, so an agent knows what to expect from a hit and a miss. For a single-parameter read-only card tool, nothing needed to select or call it correctly 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?

Schema description coverage is 100%, and the single parameter's schema text already says CIK is preferred and tickers are resolved. The description largely restates that (digit string or int resolves directly), adding only marginal confirmation rather than new syntax or failure behavior. Baseline 3 is appropriate when the schema already carries the parameter 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 concrete artifact — one IPO offering + lockup card per issuer — names its sources (424B4 prospectus joined to the catalyst lockup schedule) and its coverage (98.3% of the catalyst IPO universe, 2,522 issuers). It explicitly positions itself against siblings by naming sections__ipo_screen and sections__ipo_risk_factors, so an agent can distinguish it 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?

The 'Pairs with' sentence gives clear sequencing context: screen first to find the IPO, then pull the card, then pull risk factors. The status enum also tells the agent what a miss looks like (lockup_only, not_in_universe with the 'IPO'd long ago' example), which is practical when-not guidance. It stops short of an explicit routing rule against non-named siblings such as sections_ipo_financials.

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