Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Catalyst Calendar (PDUFA / IPO lockup / debt maturity — forward + trailing dated catalysts with provenance)

catalyst_calendar
Read-onlyIdempotent

Forward (or trailing) calendar of dated NON-EARNINGS catalysts — PDUFA goal dates / AdCom dates, IPO lock-up expiries, and corporate-bond maturity walls. The 'what's coming' companion to upcoming_earnings, merged across event types into one uniform record so an analyst-LLM can reason across catalyst types with one shape.

Eleven event types (event_type filter):

  • pdufa — FDA decision dates. 8,177 events 2015→ from SEC filings + 2,654 from press releases, LLM-extracted; outcomes auto-resolved against Drugs@FDA. Status: pending / extended / approved / crl / withdrawn / projected (v1.5 calibrated PDUFA windows, is_confirmed=false) / unresolved (still pending or extended more than 180 days past the goal date with no approval, CRL or withdrawal found: outcome unknown, no longer a forward catalyst; since 2026-11-09). Confidence is certainty of the DATE — stated PDUFA ~0.9+, vague window ~0.4-0.6. is_confirmed=true means an explicitly stated date. Calibration vs Drugs@FDA: conf≥0.9 bucket = medAE 5d / 23% exact-on-date / median −1d (FDA acts on or before deadline). Big-pharma names (BMY/PFE/MRK/AZN/REGN) come from the news pass.

  • adcom — FDA Advisory Committee meeting dates (added 2026-06-18). Sibling of pdufa; status='adcom_scheduled' for forward or window-only dates, 'adcom_held' once an exact-date meeting is before as_of or its vote is public by as_of (since 2026-11-09). Filter by event_type='adcom' if you only want AdCom dates (previously these were nested under pdufa's detail.catalyst). Sample evidence: 'FDA's Pulmonary-Allergy Drugs Advisory Committee (PADAC) met on...' — narrative text from the SEC filing or PR.

  • ipo_lockup — IPO lock-up expiry dates. 2,572 genuine IPOs since 2020 (SPAC-excluded by default). Dates are deterministic (anchor date + lockup days). Terms enriched from IPO filings for 362/480 operating 2024-2026 IPOs; pre-2024 carry the 180-day default (confidence 0.5, is_confirmed=false). Status: upcoming / early_release_eligible / passed.

  • debt_maturity — corporate bond maturities (the 'debt wall' question). Wraps the tranche N-PORT-P panel — par values are fund-held sample only (~$3T), NOT total debt outstanding. Dates are contractual (exact). Confidence 1.0. Use min_par to floor on fund-held par (default $50M).

  • clinical_readout — forward Phase 2/3 trial data-readout dates (topline / interim / proof_of_concept) extracted from biotech press releases. Mostly vague windows — date_range is the signal, not event_date alone. Confidence reflects certainty of the READOUT DATE (exact stated date ~0.75; firm 'on track for Q4 2026' ~0.6; vague 'data in 2027' ~0.4). is_confirmed=true only on exact stated dates (rare). detail carries drug, trial_name, indication, phase, readout_type, is_preclinical (true = lower-value animal/NHP readout — filter via min_confidence if you want to exclude).

  • device_panel — FDA device advisory-committee meetings (added 2026-06-28). Device sibling of adcom. In both snapshot and history (past as_of queries route to history just like adcom).

  • device_pma — device PMA approvals (status='approved') + forward decision windows (status='projected'). Device sibling of pdufa. In both snapshot and history.

  • cms_coverage — Medicare coverage events. Status: granted / denied / restricted / delayed / pending. Snapshot-only (no history table for CMS) — past-as_of queries fall back to snapshot for this type, same as debt_maturity and clinical_readout.

  • cms_coverage and cms_star_ratings are the two CMS catalyst types. cms_star_ratings (added 2026-06-28, second batch) is the annual CMS Medicare Advantage Star Ratings release (forward ~October), per public insurer (UNH/HUM/CVS/ELV/CNC/MOH/ALHC/CLOV). detail carries overall stars + YoY + 4.0-cliff proximity. Snapshot-only (no history table).

  • foreign_permit (added 2026-07-03) — foreign government-approval calendar. MVP scope: CNSC nuclear licensing hearings (Canada), covering uranium/nuclear developers with a US ticker (e.g. NXE Rook I, DNN Wheeler River). detail carries {regulator, sub_type, us_ticker, is_developer, applicant, matter, decision_class, estimated_decision, outcome}. Snapshot-only — past-as_of falls back to snapshot, same as cms_coverage / cms_star_ratings. Broader jurisdictions may follow.

  • cms_rate_notice (added 2026-07-10) — CMS Medicare Advantage Rate Notice, per public insurer (HUM/UNH/CVS/CNC/ELV/...). Advance + Final milestones; the Final Rate Announcement lands ~statutory first Monday of April. Snapshot-only (no history table) — past-as_of falls back to snapshot.

  • tariff (added 2026-07-13) — Section 232 / 301 tariff actions across 12 commodities (copper, steel, aluminum, semiconductors, critical minerals, pharma, timber, autos, aircraft, trucks, polysilicon, drones). Federal-Register-sourced (proclamations / BIS / USTR notices — every row carries its FR document number + URL), deterministic, no LLM. History-eligible — the core query is a past-as_of read: "what was copper's 232 status on 2025-09-01?" → in_effect (50% since 2025-08-05). Milestones: investigation_opened → proclamation → (rescinded); status ∈ under_investigation / in_effect / etc. detail carries statute / commodity / milestone / status / effective_date / proclamation_ref / federal_register_url + the live current_status / current_rate_pct / current_since so one call answers "status on date X" without interval math. ⚠ rate_pct is deliberately NULL on multi-rate documents — a 232 proclamation cites market-share statistics, recommendations, and multiple enacted rates in one legal instrument; a wrong tariff rate on an auto-consumed feed is unrecoverable, so when a document enacts >1 rate we hand over rates_enacted[] + the FR link instead of guessing (copper's enacted 50% IS populated). Per-HTS rates are a v2 ask (needs HTS tables, not proclamation prose).

Inputs (all optional):

  • tickers — list of tickers; omit for cross-name screen. NB: ~30% of debt_maturity rows have ticker=null (debt-only financing subs without an equity ticker — Ford Motor Credit, Toyota Motor Credit, etc.); use the cik field on the returned row to identify those.

  • event_types — list of {pdufa, adcom, ipo_lockup, debt_maturity, clinical_readout}; omit for all.

  • window_days — forward (or trailing when include_passed=true) window in days from as_of. Default 90. Ignored when window_start/window_end set.

  • window_start / window_end — explicit YYYY-MM-DD bounds on event_date.

  • as_of — point-in-time date (YYYY-MM-DD). Default today. PIT replay is now honest (2026-06-15 + widened 2026-06-17): whenever the query REACHES INTO THE PAST — as_of < today OR include_passed=true OR window_start before today — pdufa + ipo_lockup queries route to catalyst_calendar_history (~5.4k rows, validity ranges; full resolved-outcome record approved/crl/ withdrawn back to 2015). Snapshot carries resolved outcomes only within its ±731d bake window, so deep include_passed base-rate sweeps MUST hit history to get the full picture. as_of today/future + forward-only window, or any debt_maturity / clinical_readout query, hits catalyst_calendar_snapshot. source_table per row + sources_used at the top reflect which path produced each row. debt_maturity + clinical_readout are NOT in history (maturity dates are static/public from issuance; clinical readouts are too new and disclosure-sourced — past-as_of of either falls back to snapshot).

  • data_health (on every response): per-event-type feed freshness + audit status so an auto-consuming system can detect a STALE or BLIND feed and refuse to trade on it. status ∈ {ok, stale, critical, unknown}; per_type reports only the event_types returned (freshness_class + is_stale + hours_since + row_count); audit_passing says whether what we serve matches reality (Federal Register / Drugs@FDA recall). When degraded, a top-level health_alert ⚠ leads the response. row_count=0 for a type ⇒ critical (zero rows is indistinguishable from 'nothing scheduled' — that's exactly how the adcom bug hid for weeks).

  • min_confidence — 0.0-1.0 floor (default 0.3). Drops vague-window rows for the conservative path; pass 0.0 to see everything.

  • include_passed — when true, include events whose event_date < as_of. Default false (forward-only). For pdufa+ipo_lockup, also routes the query to catalyst_calendar_history for full resolved-outcome coverage back to 2015.

  • min_par — for debt_maturity rows, minimum fund-held par in USD (default $50M = 50_000_000). Applies ONLY to debt rows; pdufa/lockup rows pass through.

  • sort_by — date (default, ASC) or confidence (DESC).

  • limit — max rows returned (default 50, max 500).

Response shape — one row per catalyst, common record: {cik, ticker, company_name, event_type, event_date, date_range, days_until, confidence, is_confirmed, status, headline, detail (jsonb per-type — see below), evidence, source_accession, source_type, source_date}.

detail blob per type:

  • pdufa: {catalyst: pdufa|adcom, drug, indication, review_type}

  • adcom: also vote (list of {question, yes, no, abstain, favorable} per voting question; favorable = the majority outcome favors approval, polarity handled), vote_outcome (favorable / unfavorable / mixed), vote_source (news:, the sponsor press release) and vote_source_date. All null when no tally is known; a vote shows only when vote_source_date <= as_of. Coverage: AdComs with ticker-tagged news, so some older or no-vote meetings have no tally.

  • ipo_lockup: {ipo_date, lockup_days, tranche, ipo_type, shares_locked, locked_pct_of_total, early_release_trigger, holder_types}

  • debt_maturity: {cusip, coupon, fund_held_par, n_funds, note} (note flags the fund-held N-PORT sample caveat)

Provenance: every row carries source_accession, source_type (filing/news/fda/tranche), source_date (PIT key — what made this knowable).

Console Catalyst Calendar parity (2026-10-12) — added inputs window (7 / 30 / 90 / 180, alias of window_days), types (alias of event_types), sector (SIC description substring or 2-digit SIC), min_market_cap (USD, approximate cap), q (company name / ticker substring). Two more event types: listing_deadline — open exchange-compliance deadlines (a notice is open until its deadline passes, the company regains compliance, or for a late-filing notice a later 10-K / 10-Q is filed); earnings — PROJECTED earnings dates (estimates, $10B+ market cap by default, earnings_min_market_cap to change; any cap when tickers is given). Every row now carries group (Healthcare / Capital markets / Policy / Credit / Earnings), market_cap_approx (earnings panel, not Console's guarded cap) and sector_sic; the response has by_group counts. Console defaults: confidence ≥ 0.4 and debt maturities OFF unless types / event_types names debt_maturity or include_debt=true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "catalyst_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCompany name or ticker substring.
as_ofNoPoint-in-time date (YYYY-MM-DD). Default today. See description re: v1 historical-replay caveat.
limitNoMax rows returned (default 200 when no event types are given — the cut is shared across groups; 50 otherwise; max 500). n_total / truncated / by_group always describe the whole window.
typesNoAlias of event_types (Console naming).
sectorNoSIC description substring (e.g. 'pharmaceutical') or 2-digit SIC prefix (e.g. '28').
windowNoAlias of window_days (Console naming).
min_parNoFor debt_maturity rows only, minimum fund-held par in USD (default 50000000 = $50M). Pdufa/ipo_lockup rows pass through.
sort_byNodate = event_date ASC (default), confidence = confidence DESC.date
tickersNoList of tickers to scope. Omit for cross-name screen.
window_endNoExplicit upper bound on event_date (YYYY-MM-DD).
event_typesNoRestrict to one or more event types. Omit for all (debt_maturity excluded unless include_debt=true).
window_daysNoForward window in days from as_of (default 90). Ignored when window_start/window_end set.
include_debtNoInclude debt_maturity rows when event_types/types is omitted (Console default: off).
window_startNoExplicit lower bound on event_date (YYYY-MM-DD).
include_passedNoWhen true, include events whose event_date is in the past relative to as_of. Default false.
min_confidenceNo0.0-1.0 confidence floor on the date (default 0.4, Console's floor).
min_market_capNoMinimum approximate market cap in USD (earnings panel).
earnings_min_market_capNoMarket-cap floor for projected earnings rows when no tickers are given (default $10B).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: point-in-time semantics, snapshot-vs-history fallback per event type, the deliberate NULL rate_pct on multi-rate tariff documents, the fund-held-par sampling caveat on debt_maturity, and the data_health/stale-feed contract. These are non-obvious behaviors an agent could not infer from the schema or annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is severely oversized — thousands of words of per-type essays, inline '(added 2026-07-13)' changelog stamps, row counts, calibration statistics, and warning glyphs. Bullets provide some structure and the first sentence is front-loaded, but the signal-to-noise ratio is poor and key operating rules are buried in the middle of long entries.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 14 event types, 18 parameters, and no output schema, the description does supply the response row shape, the per-type detail blob contents, and provenance fields, so an agent can call and interpret it. Completeness is undercut by the stale defaults it states and by burying operational rules inside type-by-type prose rather than a stable reference section.

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?

With 100% schema coverage the baseline is 3, and the description does add real meaning: ticker=null on ~30% of debt rows with cik as the fallback identifier, min_par applying only to debt rows, and window_start/window_end overriding window_days. It loses a point because several stated defaults have drifted out of sync with the schema (description says min_confidence default 0.3 and limit default 50; schema says 0.4 and 200-without-event-types), which can mislead an agent that reads only the prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb+resource+scope ('forward (or trailing) calendar of dated NON-EARNINGS catalysts') and explicitly positions itself against the sibling upcoming_earnings as its 'what's coming' companion. The core purpose is unambiguous, but it is immediately submerged under per-event-type encyclopedic detail that a first-time reader must wade through to confirm the one-line answer.

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?

Genuinely strong routing guidance: it says when queries reach into the past they hit catalyst_calendar_history versus catalyst_calendar_snapshot, which types are snapshot-only (cms_coverage, debt_maturity, clinical_readout), and how to exclude low-value rows via min_confidence. It falls short of 5 because the guidance is entangled with internal implementation notes and changelog dates rather than a clean when/when-not block, and no explicit exclusion cases are stated up front.

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