Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

FDA Inspections (NAI/VAI/OAI classifications — the EARLY enforcement signal)

bio_inspections
Read-onlyIdempotent

FDA inspection classifications (NAI / VAI / OAI) by recipient — the EARLY enforcement signal, often months before a Warning Letter. Use to answer 'every OAI in oncology pharma since 2024' / 'has this CDMO had any OAIs' / 'what does this sponsor's inspection record look like.'

Classification codes (the load-bearing field):

  • OAI (Official Action Indicated) — regulatory/legal action warranted. The bad one. Often the upstream signal of a coming Warning Letter or import alert.

  • VAI (Voluntary Action Indicated) — observations noted, voluntary correction.

  • NAI (No Action Indicated) — clean inspection.

Use worst_only=true as a convenience for classification='OAI' — the high-signal subset for sponsor risk screening.

Inputs (all optional; pass at least one of ticker_or_cik / company / classification for a meaningful query):

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

  • company — ILIKE substring on legal_name. Use for CDMOs (Catalent, Lonza, WuXi, Patheon, Thermo Fisher), foreign API makers, or BIMO clinical investigators that aren't in super_bio's sponsor universe.

  • classification — exact match on classification_code: 'OAI' / 'VAI' / 'NAI'. Mutually compatible with worst_only (worst_only wins if both set).

  • worst_only — bool convenience for classification='OAI'. Default false.

  • project_area — substring match: 'Drug Quality Assurance' / 'Bioresearch Monitoring' (BIMO clinical trial sites) / 'Human Cellular, Tissue, and Gene Therapies' / etc.

  • since — ISO date floor on classification_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 {inspection_id, fei_number, legal_name, city, state, country_name, fiscal_year, project_area, product_type, classification_code, classification, classification_date, posted_citations, matched_cik, matched_ticker, matched_method, matched_confidence, is_cdmo} rows sorted by classification_date DESC. fei_number is FDA's Establishment Identifier — useful for joining unmatched sites and for tracking site-level history across multiple owners.

Coverage (substrate live 2026-06-18): 26,133 classified inspections since 2015 across Drugs + Biologics (Biologics scope captures CBER cell/gene-therapy site inspections). Mix: OAI 453 / VAI 9,313 / NAI 16,367. ~50% matched to a super_bio sponsor; unmatched rows are mostly foreign API makers, CDMOs, and BIMO clinical investigators (surface via company ILIKE).

Pairing with bio_warning_letters: same recipient, two enforcement stages. Recommended consumer pattern: query bio_inspections(worst_only=true) for the EARLY signal, then bio_warning_letters for the escalation. An OAI with no subsequent Warning Letter is itself informative (issue may have been resolved at the 483 stage).

Verified spec cases (live 2026-06-18): company='Catalent', classification='OAI' → Catalent Indiana, LLC · 2025-11-24 · OAI · Drug Quality Assurance · ticker=CTLT — the canonical CAPR-class case, sitting 4 days BEFORE the CTLT Warning Letter 2025-11-20 (the inspection IS what the Warning Letter later escalated); worst_only=true, since='2024-01-01' → all OAIs since 2024 (highest-signal subset for sponsor risk screening); project_area='Human Cellular, Tissue, and Gene Therapies' → cell/gene therapy site inspections.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 50, max 500).
sinceNoISO date floor on classification_date (default 2015-01-01).
companyNoILIKE substring on legal_name. Use for CDMOs / foreign API makers / BIMO sites not in super_bio universe.
worst_onlyNoConvenience for classification='OAI'. Default false. Wins if both set.
project_areaNoSubstring match on project_area: 'Drug Quality Assurance' / 'Bioresearch Monitoring' (BIMO clinical trial sites) / 'Human Cellular, Tissue, and Gene Therapies' / etc.
ticker_or_cikNoEquity ticker (e.g. 'CTLT') or SEC CIK integer.
classificationNoExact match on classification_code: 'OAI' / 'VAI' / 'NAI'.
min_confidenceNoFloor on matched_confidence (default 0.85). Only applies when filtering by ticker_or_cik.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive), and the description adds non-obvious behavioral context beyond them: only ~50% of rows match a sponsor, unmatched rows must be surfaced via company ILIKE, min_confidence only applies to ticker_or_cik queries, and worst_only silently overrides classification. The coverage statistics and default date floor further reduce surprise.

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 and the load-bearing classification legend are front-loaded, but roughly half the text restates parameters the schema already documents verbatim at 100% coverage, which is redundant. The 'verified spec cases' block also contains a self-inconsistent claim (a 2025-11-24 OAI described as '4 days BEFORE' a 2025-11-20 Warning Letter), which is noise an agent must reconcile.

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, and the description fully compensates by enumerating the returned row fields, sort order, and the use of fei_number for joining and site-level history. Combined with coverage counts and matching caveats, an agent has everything needed to call this correctly and interpret results.

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 schema already documents all eight parameters; the description nonetheless adds real meaning — the worst_only/classification precedence rule, the coupling of min_confidence to ticker_or_cik with a suggested 0.5 for name_overlap matches, and example project_area values. The worked examples turn abstract filters into concrete call shapes.

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 (FDA inspection classifications NAI/VAI/OAI by recipient) and its analytical role (early enforcement signal). It explicitly differentiates from the sibling bio_warning_letters as a distinct enforcement stage, so an agent can choose between them 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 user-question phrasings it answers ('every OAI in oncology pharma since 2024', 'has this CDMO had any OAIs'), directs which parameter to use for in-universe sponsors vs. CDMOs/foreign API makers/BIMO sites, and prescribes a sequencing pattern (inspections first, then bio_warning_letters for escalation). This is explicit when-to-use plus an alternative.

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