Skip to main content
Glama

FDA drug recall enforcement reports matching a product

health_fda_recalls_enforcement
Read-only

FDA drug recall enforcement reports (openFDA) matching a product word: recall number, class I/II/III, status, recalling firm, reason, product description and dates. Drug recalls only, not food or cosmetics. Up to 10 per call. Related tools on this server, for a different need: health_fda_adverse_events_faers when you need FDA FAERS drug adverse event reports for a generic drug; health_fda_drug_shortages when you need FDA drug shortage listings: generic name, availability. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "health_fda_recalls_enforcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesProduct word, letters and spaces, 2 to 60 characters
maxNoHow many reports, 1 to 10 (default 5)

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
sourceNo
recallsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses pricing, payment networks, that failed calls are not charged, and a per-call result cap of 10. It also identifies the openFDA source and drug-only coverage, which are meaningful behavioral constraints.

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?

The description is front-loaded and efficient, with scope, output fields, alternatives, and pricing in a single paragraph. It is slightly dense and lists return fields that the output schema may already cover, but nothing is clearly wasteful.

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 a two-parameter, read-only lookup with full schema coverage and an output schema, the description supplies everything an agent needs: scope, result limit, alternatives, source, and payment behavior. No material calling detail is missing.

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%, and the description adds little beyond the schema for q and max. It repeats that q is a product word and that results are capped at 10, but does not add syntax or filtering nuances.

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?

The description states a specific verb and resource: FDA drug recall enforcement reports matching a product word. It lists the exact report fields and explicitly excludes food and cosmetics, making the scope distinguishable from near alternatives.

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?

It explicitly redirects to health_fda_adverse_events_faers for FAERS adverse event reports and health_fda_drug_shortages for shortage listings. The drug-only scope also tells the agent when this tool is not appropriate.

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