Skip to main content
Glama

get_fda_recall_history

Read-only

Use when evaluating a pharmaceutical company, medical device manufacturer, or healthcare vendor for product safety risk, supply chain exposure, or regulatory compliance standing. Returns FDA recall classifications (Class I = risk of serious harm, Class II = moderate risk, Class III = unlikely to cause harm) with product descriptions and recall reasons. Class I recalls trigger mandatory FDA press releases and procurement review obligations. Example: MedSupply Corp — 2 Class I drug recalls in 36 months: contaminated IV solutions (2022) and mislabeled injectable (2023) — pattern of serious quality control failures requiring immediate vendor review. Source: OpenFDA Enforcement Reports. $0.10 USDC per call.

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": {
      "company_name": "<company_name>"
    },
    "name": "get_fda_recall_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_nameYes
product_typeNoboth

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world, non-destructive profile, and the description adds real context beyond them: the Class I/II/III meaning, the downstream consequence of Class I recalls (press releases, procurement review obligations), the OpenFDA data source, and a per-call cost. It does not discuss pagination or historical depth limits.

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?

Purpose, classification legend, and usage conditions are front-loaded, and the pricing/source details sit at the end where they belong. The multi-year MedSupply Corp example is longer than strictly necessary but does concretely illustrate output shape and interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 helpfully characterizes the return contents and severity semantics, which covers a lot of ground. However, a two-parameter tool with 0% schema coverage leaves the product_type filter unexplained, so an agent cannot tell how that parameter changes results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it does not: neither company_name nor the product_type enum (drug/device/both) is mentioned or explained. The worked example only implies a company-name query, leaving the filter parameter's behavior entirely undocumented.

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 (FDA recall classifications with product descriptions and recall reasons) and the entities it covers (pharmaceutical, device, healthcare vendor). It is clearly distinguishable from a generic drug-recall lookup, though it never explicitly contrasts itself with the sibling get_drug_recall_status.

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?

It gives explicit when-to-use framing: product safety risk, supply chain exposure, regulatory compliance standing for pharma/device/vendor evaluation. There are no stated exclusions or named alternative tools for overlapping cases, so it falls short of a 5.

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