Skip to main content
Glama

get_drug_recall_status

Read-only

Use when a pharmacy, supply chain, or compliance agent needs FDA drug recall status for an NDC or drug name. Returns recall records (status, classification, reason, dates), match_confidence (ndc_exact or name_match), normalized ndc11, and openFDA provenance — never silently returning a different product's recalls. Example: NDC 41163-703-10 — Class II nasal spray recall records with termination dates. Source: openFDA drug/ndc and drug/enforcement. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_sources[] discloses provenance bound by synthesis.output_hash.

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": {
      "ndc_or_name": "<ndc_or_name>"
    },
    "name": "get_drug_recall_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
ndc_or_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses the return shape (status, classification, reason, dates), the match_confidence contract (ndc_exact vs name_match), normalized ndc11, and an explicit no-silent-mismatch guarantee. It also states operational behavior an agent cannot infer from annotations: $0.10 USDC per call, HTTP 503 with no charge when upstream is unavailable, and provenance disclosure via data_sources[].

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 usage condition and resource are front-loaded, and the example grounds the abstract description. The trailing '|' -separated SLA/provenance clause and the 'bound by synthesis.output_hash' phrase are dense internal jargon that add length without much decision value for an agent.

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?

No output schema exists, so the description correctly compensates by enumerating returned fields and the confidence enum. For a one-parameter lookup tool this is nearly complete; only NDC input formatting and the exact meaning of the provenance hash are left unstated.

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?

With a single parameter and 0% schema description coverage, the description carries the full burden — and it does explain that ndc_or_name accepts either an NDC or a drug name, plus that name inputs yield name_match with reduced confidence versus ndc_exact. It does not specify accepted NDC formatting (hyphenated vs 11-digit) or name-matching tolerance, leaving some input-shaping ambiguity.

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 verb and resource — FDA drug recall status — plus the accepted identifiers (NDC or drug name) and the domain audience. It is clear what the tool does, but it never distinguishes itself from the sibling get_fda_recall_history, so an agent comparing the two has no stated basis for choosing between them.

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?

'Use when a pharmacy, supply chain, or compliance agent needs...' gives a concrete usage condition tied to caller roles and a worked example (NDC 41163-703-10). It stops short of when-not-to-use or naming an alternative sibling, but the positive context is explicit rather than implied.

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