Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

FDA Warning Letters (late-stage enforcement by recipient — CDMO + sponsor)

bio_warning_letters
Read-onlyIdempotent

FDA Warning Letters by recipient — late-stage public enforcement actions. Use to answer 'has this company received a Warning Letter' / 'every CGMP warning letter to a CDMO since 2024' / 'OMQ enforcement against this sponsor.' Returns letter date + issuing office (CDER/CBER/OMQ/etc.) + subject (typically CGMP / Finished Pharmaceuticals / Adulterated) + response / closeout flags.

Inputs (all optional, but pass at least one of ticker_or_cik / company / issuing_office for a meaningful query):

  • ticker_or_cik — equity ticker or SEC CIK. Filters to letters where super-bio's matcher resolved the recipient to a super_bio sponsor.

  • company — ILIKE substring match on company_name. Use this for CDMOs / contract manufacturers (Catalent, Lonza, Patheon, Thermo Fisher, etc.) that aren't in super_bio's sponsor universe but still receive Warning Letters.

  • issuing_office — substring match: 'Office of Manufacturing Quality' / 'OMQ' / 'CDER' / 'CBER' / etc. The OMQ subset is the high-signal cohort for supply-chain trades (manufacturing-quality warnings frequently precede import alerts or product shortages).

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

  • min_confidence — float in [0.0, 1.0], default 0.85. Only applies when filtering by ticker_or_cik (forces tight matches). Set to 0.5 to also see name_overlap matches.

  • limit — default 50, max 500.

Response shape: list of {company_name, letter_issue_date, posted_date, issuing_office, subject, has_response, has_closeout, matched_cik, matched_ticker, matched_method, matched_confidence} rows sorted by letter_issue_date DESC.

Critical caveat — interpret a NULL result correctly. Warning Letters are the LATE-stage enforcement signal. Most pharma FDA enforcement appears in inspection classifications (NAI / VAI / OAI) which are NOT in this table (super-bio §5 #25, pending FDA Data Dashboard API key). An empty result for a sponsor means 'no Warning Letter (yet)' — NOT 'no FDA issues.' For inspection classifications you'd need to wait for the OAI ingestion to land.

Verified spec cases (live 2026-06-18): company='Catalent' → 1 row (Catalent Indiana, LLC · 2025-11-20 · CGMP/Finished Pharmaceuticals/Adulterated · Office of Manufacturing Quality — the CAPR-class verify case); issuing_office='Office of Manufacturing Quality', since='2024-01-01' → all manufacturing-quality letters since 2024 (the supply-chain catalyst cohort).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows returned (default 50, max 500).
sinceNoISO date floor on letter_issue_date (default 2015-01-01).
companyNoCase-insensitive ILIKE substring on company_name. Use for CDMOs / non-super_bio-universe recipients (Catalent, Lonza, Patheon, etc.).
ticker_or_cikNoEquity ticker (e.g. 'SRPT') or SEC CIK integer. Filters to letters matched to a super_bio sponsor.
issuing_officeNoSubstring match on issuing_office: 'Office of Manufacturing Quality' / 'CDER' / 'CBER' / etc. OMQ is the supply-chain catalyst cohort.
min_confidenceNoFloor on matched_confidence when filtering by ticker_or_cik (default 0.85; super-bio uses 0.85 for name_token matches and ~0.60 for name_overlap).

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 safety (readOnly, idempotent, non-destructive), and the description goes well beyond them: it discloses default thresholds (min_confidence 0.85, since 2015-01-01), that min_confidence only applies when filtering by ticker_or_cik, sort order (letter_issue_date DESC), and a critical interpretation caveat that an empty result means 'no Warning Letter yet,' not 'no FDA issues.' That NULL-semantics warning is exactly the kind of behavioral context annotations 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 purpose, then inputs, response shape, and the caveat in a sensible order; headers make it scannable. It is longer than strictly necessary — the 'Verified spec cases' block with specific dates and the 'CAPR-class verify case' aside read as internal QA notes rather than agent-facing guidance, though the example queries themselves are useful.

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, but the description supplies the full row shape and field list, so return values need no further explanation. Combined with defaults, sort order, and the empty-result interpretation, an agent has everything needed to call this correctly and to report its output honestly.

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 the baseline would be 3, but the description adds cross-parameter semantics the schema does not: at least one of ticker_or_cik/company/issuing_office should be supplied for a meaningful query, ticker_or_cik resolves through a matcher to a sponsor, company is the escape hatch for non-universe CDMOs, and min_confidence is scoped to ticker_or_cik filtering only with the 0.5 threshold unlocking name_overlap matches.

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 resource and scope: FDA Warning Letters filtered by recipient, explicitly framed as 'late-stage public enforcement actions.' It also distinguishes itself from adjacent signal types (inspection classifications NAI/VAI/OAI, which it says are NOT in this table), so an agent can tell it apart from bio_inspections 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 concrete trigger questions ('has this company received a Warning Letter', 'every CGMP warning letter to a CDMO since 2024') and routes by recipient type: ticker_or_cik for super_bio sponsors vs. company for CDMOs/contract manufacturers outside the sponsor universe. It also names the OMQ subset as the high-signal cohort for supply-chain use cases, which is genuine when-to-use guidance rather than restatement.

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