Skip to main content
Glama

Stratalize Intelligence

Get Fda Recall History

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

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

Beyond the readOnly/openWorld annotations it discloses the data source (OpenFDA Enforcement Reports), the meaning of each recall class, the downstream consequence of Class I recalls (mandatory press releases, procurement review obligations), and a per-call price of $0.10 USDC. That is meaningful operational context; only return volume, time coverage, or empty-result behavior are unaddressed.

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?

It is front-loaded with the trigger condition, then the return content, then escalation context, then source and price — a sensible order with no filler sentences. The worked example is longer than strictly necessary but earns its place by demonstrating the risk signal.

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?

With no output schema, the description does its duty by naming the fields returned (classifications, product descriptions, recall reasons) and by explaining what the class codes mean. The remaining gap is parameter-level guidance for a 2-parameter tool with zero schema coverage.

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 parameter meaning, and it does not: neither company_name nor the product_type enum (drug/device/both, defaulting to both) is mentioned or explained. The example implies a company name input but gives no guidance on naming format or on when to narrow product_type.

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 opens with a concrete verb and resource — returns FDA recall classifications — and names the entity types it covers (pharma company, device manufacturer, healthcare vendor), which lets an agent tell it apart from generic enforcement-history tools. It stops short of explicitly distinguishing itself from close siblings such as 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 states clear use conditions: product safety risk, supply chain exposure, and regulatory compliance standing, plus a worked scenario (vendor review after Class I recalls). There are no explicit when-not conditions or named alternative tools, which keeps it below 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