Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

FDA Approvals (NDA/BLA action dates by ticker/CIK/drug — authoritative post-event anchor)

bio_fda_approvals
Read-onlyIdempotent

Historical FDA NDA/BLA approvals — the PIT-authoritative action dates (submission_status_date) per sponsor / brand / active_ingredient. Use to answer 'what has this company been approved for' / 'when did evolocumab clear' / 'how many BLAs in oncology since 2020.' Pairs with catalyst_calendar(pdufa) for the forward calendar and bio_similar_setups for the post-approval comparable cohort.

Coverage (substrate refreshed 2026-06-17): 1,388 NDA/BLA originals since 2015 — 1,363 CDER (openFDA drugsfda pull) + 25 CBER (curated cell/gene/CAR-T cohort). 645+ matched to cik/ticker (CBER match rate 72% — cell/gene sponsors are biotech-pure-play) via super-bio's brand_exact / brand_alias / ingredient_exact / brand_partial matchers with matched_confidence ∈ [0.5, 1.0]. Supplements (sBLA / sNDA) excluded by default — pass originals_only=false to include them.

Inputs (all optional, at least one of ticker_or_cik / drug / modality recommended):

  • ticker_or_cik — equity ticker or SEC CIK. Filter to one company.

  • drug — ILIKE substring match against brand_name OR active_ingredient (case-insensitive). Either brand (REPATHA) or INN (evolocumab) works.

  • modality — drug-class filter: 'CAR-T' / 'gene_therapy' / 'cell_therapy' / 'mAb' / 'mAb_bispecific' / 'small_molecule' / 'siRNA' / 'antisense_oligo' / 'peptide' / 'protein'. Use this for 'every approved cell/gene therapy' or 'every CAR-T approval' queries — these are the CBER-class rows the modality column was added for. Filter is exact-match on the modality column.

  • since — ISO date floor on submission_status_date (default 2015-01-01).

  • originals_only — bool, default true. False to include supplements (sNDA / sBLA).

  • min_confidence — float in [0.0, 1.0], default 0.85. Higher = stricter ticker/cik match precision. Important caveat (super-bio note): when matched_confidence < 0.9, prefer sponsor_name for filer-correctness — the ticker/cik might be a licensee rather than the original developer. This is especially true for CBER (cell/gene) rows where the approval may have been transferred to a downstream developer.

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

Foreign-private-issuer caveat (super-bio note): 20-F filers in the bio cohort (ARGENX, BNTX, LEGN) aren't in super-bio's universe yet (queued as FUTURE_DIRECTIONS §5 #13). For those, the ticker/cik match either lands on a US licensee (Vyvgart → ZLAB) or cik=NULL. When cik IS NULL but the approval is clearly the foreign filer's drug (recognize via sponsor_name), interpret accordingly.

Response shape: list of {application_number, submission_number, fda_action_date, sponsor_name, brand_name, active_ingredient, modality, source, cik, ticker, matched_method, matched_confidence} rows sorted by submission_status_date DESC. source ∈ {'CDER', 'CBER'} disambiguates row origin. Plus as_of_effective, n_returned, filters_applied.

Live verified spec cases: ticker_or_cik='TVTX' → 3 originals (THIOLA EC 2019-06-28, FILSPARI 2023-02-17, VOYXACT 2025-11-25); drug='evolocumab' → REPATHA AMGN 2015-08-27 (+ 2021 supplement when originals_only=False); ticker_or_cik='REGN', since='2020-01-01' → INMAZEB BLA761169 2020-10-14, EVKEEZA BLA761181 2021-02-11, +6 more; modality='CAR-T' → 7 rows (KYMRIAH 2017-08-30, YESCARTA 2017-10-18, TECARTUS 2020-07-24, BREYANZI 2021-02-05, ABECMA 2021-03-26, CARVYKTI 2022-02-28, AUCATZYL 2024-11-08); modality='gene_therapy' → 12 rows (LUXTURNA 2017-12-19 → BEQVEZ 2024-04-25); modality='cell_therapy' → 6 rows (STRATAGRAFT → RYONCIL — the CAPR-class reference set).

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": "bio_fda_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugNoDrug name — case-insensitive ILIKE substring against brand_name OR active_ingredient. 'REPATHA' or 'evolocumab' both work.
limitNoMax rows returned (default 50, max 500).
sinceNoISO date floor on submission_status_date (default 2015-01-01 — the coverage start).
modalityNoFilter by drug class: 'CAR-T' / 'gene_therapy' / 'cell_therapy' / 'mAb' / 'mAb_bispecific' / 'small_molecule' / 'siRNA' / 'antisense_oligo' / 'peptide' / 'protein'. Use for 'every approved cell/gene therapy' queries — the CBER-class rows added 2026-06-17.
ticker_or_cikNoEquity ticker (e.g. 'AMGN') or SEC CIK integer. Filters approvals to one company.
min_confidenceNoFloor on matched_confidence (default 0.85 for company-scoped queries; auto-lowered to 0.0 when `modality` is set without ticker_or_cik, because the caller wants every approval of that class — CBER rows often have low/zero confidence since the foreign/private cohort isn't fully matched). Lower for broader recall; when < 0.9 prefer sponsor_name over ticker/cik for filer-correctness.
originals_onlyNoDefault true (submission_number='1' only). False to include supplements (sNDA / sBLA — labeling expansions, new indications, etc.).
exclude_biosimilarNoExclude biosimilar/generic approvals (super-bio T030 `biosimilar` flag — FDA -xxxx suffix, disambiguated from suffixed ORIGINATOR biologics by filing sponsor). Default false = every row carries `biosimilar` so you can filter yourself. Set true for ORIGINATOR catalyst events (a company's own new drugs, not its or competitors' biosimilars). Note: cross-company contamination is already removed at the data layer — a company only carries its OWN biosimilars now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so only extra context earns credit — and the description delivers a lot: coverage provenance (1,388 originals, CDER vs CBER split, refresh date 2026-06-17), supplements excluded by default, match-confidence mechanics, and a foreign-private-issuer caveat where ticker/CIK can silently land on a licensee. The one gap is that caveat-heavy prose is somewhat buried in bolded blocks rather than surfaced as a warning region up front.

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

Conciseness3/5

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

Purpose is front-loaded and section headings help scanning, but the definition is very long and the 'Inputs' block duplicates the already-complete schema descriptions almost sentence for sentence. The 'Live verified spec cases' paragraph is useful evidence yet runs long with per-row brand/date enumerations that mostly serve as validation rather than selection guidance.

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?

For an 8-parameter, all-optional, no-output-schema tool, the description supplies everything an agent needs: response field list, sort order, source disambiguation, default windows, confidence semantics, and known data-quality failure modes (20-F filers, cik=NULL rows). Nothing material about correct invocation is left unstated.

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 exceeds it by explaining the reasoning behind min_confidence (stricter precision, fall back to sponsor_name below 0.9 for filer-correctness) and the CBER-specific caveat that confident-looking ticker matches may be downstream licensees. It also clarifies modality is an exact-match column added specifically to capture CBER-class rows. Marginal deduction because the 'Inputs' section largely restates the schema text verbatim rather than adding new 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 ('Historical FDA NDA/BLA approvals ... action dates per sponsor / brand / active_ingredient') and immediately ties it to concrete question shapes ('what has this company been approved for', 'when did evolocumab clear'). It also explicitly distinguishes itself from adjacent tools — forward calendar via catalyst_calendar(pdufa) versus this post-event anchor — so an agent can route without inspecting schemas.

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 use cases, names the sibling tools it pairs with and the division of labor with each, and adds a class-specific routing rule ('Use this for every approved cell/gene therapy or every CAR-T approval'). The exclude_biosimilar parameter description further states when to set it (originator catalyst events vs. full row set).

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