Skip to main content
Glama

FDA drug recalls (enforcement reports)

rx_recalls
Read-only

FDA drug recall enforcement reports from openFDA, newest report first, filtered by optional drug, brand or firm text (every word must match; brand names also match their RxNorm ingredients), look-back months and FDA classification (I, II, III). Entries include recall number, classification, status, product description, reason, recalling firm, distribution pattern, initiation and report dates (ISO) and voluntary or mandated status, plus counts by classification. Price: $0.01 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": "rx_recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoDrug name, brand or recalling firm text. Omit for all recent drug recalls.
limitNoEntries to return, 1 to 50 (default 20).
monthsNoLook-back window on report date, 1 to 120 months (default 24 with q, 3 without).
classificationNoFDA recall classification filter.

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?

Goes well beyond the readOnly/openWorld annotations by disclosing the paid-call model: $0.01 per successful call in USDC via x402 v2, with failed calls and zero-match calls uncharged. It also reveals matching behavior (every word must match; brands also match RxNorm ingredients) and enumerates returned fields and classification counts.

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-loads the resource and ordering, then filters, then output shape, then pricing — a sensible order. The first sentence is long and clause-heavy, but every clause carries information an agent needs; nothing is padding.

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?

With no output schema, the description compensates by listing the returned fields and the classification counts. Combined with pricing and matching semantics, an agent has everything needed to call it and interpret the cost/result correctly.

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 baseline is 3; the description earns above that by explaining the matching semantics of q (all words must match, brand-to-ingredient expansion) and the default months behavior. It doesn't add much on limit or classification beyond the schema's own enum.

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 verb and resource ('FDA drug recall enforcement reports from openFDA'), the ordering ('newest report first'), and the available filters. This clearly separates it from siblings such as rx_shortages or rx_drug, which cover different datasets.

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 usable conditions: filters are optional, and 'Omit for all recent drug recalls' explains the unfiltered path. It lacks an explicit 'use X instead when...' pointer and doesn't call out when the look-back window should be widened, so it stops short of full when/when-not guidance.

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