Skip to main content
Glama

Fda 483 Citations

fda_483_citations
Read-onlyIdempotent

Individual Form 483 observations cited during FDA inspections, the specific CFR reference and what the investigator actually wrote. Use this to see WHY a site was cited, not just that it was. Search by firm, country, state or date range. Source: FDA Data Dashboard (OII).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "firm": "Sun Pharma",
      "limit": 25
    },
    "name": "fda_483_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
cfrNoCFR citation substring, e.g. "211.192".
firmNoFirm legal-name substring.
limitNoRows to return (default 50, max 5000).
sinceNoEarliest inspection end date, YYYY-MM-DD.
stateNoUS state, as a postal code ("NJ") or full name ("New Jersey"), both work. Foreign sites carry no state; filter those by country.
untilNoLatest inspection end date, YYYY-MM-DD.
_apiKeyNoFDA Data Dashboard credential as "email:key", the e-mail the credential was issued to, then the FDA-generated key, joined by a colon.
countryNoCountry name, e.g. "India".
fiscal_yearNoFDA fiscal year, e.g. "2026".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"FDA Data Dashboard credential as \"email:key\" — the e-mail the credential was issued to, then the FDA-generated key, joined by a colon."New value: +"FDA Data Dashboard credential as \"email:key\", the e-mail the credential was issued to, then the FDA-generated key, joined by a colon."
    • changedInput schema / properties / state / description
      Previous value: -"US state, as a postal code (\"NJ\") or full name (\"New Jersey\") — both work. Foreign sites carry no state; filter those by country."New value: +"US state, as a postal code (\"NJ\") or full name (\"New Jersey\"), both work. Foreign sites carry no state; filter those by country."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds useful provenance ('Source: FDA Data Dashboard (OII)') and the nature of the returned records, but says nothing about pagination, result caps, or the credential requirement, which is left entirely to the schema.

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?

Four short sentences, front-loaded with the differentiator before the filter list and source attribution. Every element is relevant, though the source line is more provenance metadata than actionable guidance.

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 nine-parameter, no-required-argument search tool with no output schema and full schema coverage, the description supplies enough intent and filter framing to drive correct calls. The gaps are the unmentioned CFR search capability and no note that the API credential is effectively needed.

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 coverage is 100%, so the schema already documents all nine parameters including _apiKey, fiscal_year, and the CFR substring match. The description's 'search by firm, country, state or date range' adds a helpful framing but omits the flagship cfr filter and fiscal_year, so it neither compensates nor detracts meaningfully.

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 (individual Form 483 observations) and what each record contains: the CFR reference and the investigator's actual wording. The line 'see WHY a site was cited, not just that it was' cleanly separates it from the sibling fda_inspections tool without needing to open 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear selection rationale ('WHY a site was cited, not just that it was') and enumerates the filter dimensions for use. It stops short of naming a specific alternative tool or stating exclusions, so the agent must infer that aggregate inspection records belong elsewhere.

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.