Skip to main content
Glama

Fda Import Refusals

fda_import_refusals
Read-onlyIdempotent

Shipments refused entry to the US by FDA at the border, with the refusal charges (the reason), product code and date. A leading indicator of supply risk for a foreign manufacturer. Search by firm, country, product 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": {
      "limit": 25,
      "country": "India"
    },
    "name": "fda_import_refusals"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoFirm name substring (this resource keys on FirmName).
limitNoRows to return (default 50, max 5000).
sinceNoEarliest refusal 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 refusal 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 of origin, e.g. "India".
productNoProduct-code description substring, e.g. "Antibiotic".

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.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuine context beyond that: what a record contains (refusal charges as the reason, product code, date), the source system (FDA Data Dashboard / OII), and the analytical meaning of the data. It does not mention the credential requirement, but the schema documents _apiKey fully.

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 what the data is before moving to filters and source. Every sentence carries information; nothing is padded or repetitive.

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 an eight-parameter, zero-required search tool with no output schema, the description conveys what rows represent, what fields matter, and where the data comes from. It leans on the schema and annotations for safety and parameter detail, which is reasonable, though a note on volume/limit behavior or firm-name matching would close the remaining gap.

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 description coverage is 100%, so the schema already explains every parameter in detail. The description restates the filterable dimensions (firm, country, product, date range) but omits state, and adds no format or matching semantics beyond what the schema provides. Baseline 3 is appropriate.

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 description names a specific resource (shipments refused entry to the US by FDA at the border) and the verb implicitly (search/list), plus the record contents: refusal charges, product code, date. It does not, however, differentiate itself from siblings such as fda_compliance_actions or fda_483_citations, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"Search by firm, country, product or date range" implies how to drive the tool, and the framing as a supply-risk leading indicator hints at the intent. There is no explicit when-to-use vs. when-not guidance and no named alternative among the FDA sibling tools.

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.