Skip to main content
Glama

Openfda

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fda Food Recalls

fda_food_recalls
Read-onlyIdempotent

Search FDA FOOD recall / enforcement reports (openFDA /food/enforcement) — product recalls, reasons, classification, recalling firm, distribution, and status. Use for food-safety / recall-history questions (distinct from fda_drug_recalls which covers drugs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoPagination offset (default 0) — the reported total can exceed one page of 100.
limitNoNumber of results (1-100, default 10)
queryNoOpenFDA search query (optional — omit for most recent recalls). Examples: 'reason_for_recall:"Listeria"', 'state:"CA"', 'classification:"Class I"'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / skip
      Added value: +{
+  "description": "Pagination offset (default 0) — the reported total can exceed one page of 100.",
+  "type": "number"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "reason_for_recall:\"Listeria\""
+  },
+  {
+    "limit": 30,
+    "query": "state:\"CA\""
+  }
+]
  3. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the data source and queryable fields but no additional behavioral traits like pagination behavior or response limits. With annotations handling the burden, a mid score is appropriate; there is no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. The core action, resource, content fields, and sibling differentiation are packed into a compact, front-loaded structure. Every clause earns its place.

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?

For a simple read-only search tool with three optional parameters and no output schema, the description covers the endpoint, result content, usage context, and sibling distinction. The only minor gap is that it doesn't describe default behavior when query is omitted, but the schema already states that. This is complete enough for an agent to call correctly.

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%, with each parameter (skip, limit, query) already documented including examples. The tool description adds context about what can be searched but doesn't add parameter-level semantics beyond the schema. Baseline 3 applies since the schema carries the load.

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 uses a specific verb ('Search'), identifies the resource ('FDA FOOD recall / enforcement reports (openFDA /food/enforcement)'), and lists the covered content fields (product recalls, reasons, classification, recalling firm, distribution, status). It explicitly differentiates from the sibling fda_drug_recalls, making the tool's scope unmistakable.

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 states when to use the tool ('Use for food-safety / recall-history questions') and names the alternative ('distinct from fda_drug_recalls which covers drugs'), giving the agent a clear decision rule. This is direct, actionable guidance rather than implied context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Openfda toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources