Skip to main content
Glama

Antigravity x402 & MCP Gateway

fetch_openfda_recalls

[0.005000 USDC via x402] Queries official US FDA openFDA enforcement feeds across food, drug, or medical device recalls, returning recall numbers, Class I/II/III severity, recalling firms, product descriptions, and reasons.

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": {
      "category": "<category>"
    },
    "name": "fetch_openfda_recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recall records to return (1 to 10, default 5).
queryNoOptional keyword filter across recall reason and product description (e.g., 'allergen', 'listeria').
categoryYesFDA enforcement category: 'food', 'drug', or 'device'.
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.005000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the critical non-obvious behavior: a metered cost of 0.005000 USDC via x402. It also characterizes the data source as 'official' FDA feeds and lists returned fields, but omits rate limits, pagination behavior, and data lag.

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?

A single dense sentence preceded by a bracketed price tag; the cost is front-loaded and every clause contributes (source, scope, categories, return fields). Slightly over-packed but no filler.

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 and no annotations, the description still tells the agent what the tool returns, which categories it covers, and that payment is required. That is sufficient for an agent to call it correctly without further context.

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%, so the schema already documents limit, query, category, and the payment signature token. The description adds only marginal meaning by naming the category values and result fields; it gives no query syntax or matching semantics beyond what the schema states.

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 (Queries) and resource (official US FDA openFDA enforcement feeds) scoped to food, drug, or device recalls, and enumerates the returned fields (recall numbers, Class I/II/III severity, firms, product descriptions, reasons). No sibling tool covers recalls, so the purpose is unambiguous without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage via 'Queries official US FDA openFDA enforcement feeds' and names the three categories, but never says when to choose this tool over another source or when not to use it. No prerequisites, freshness, or coverage caveats are given; the only routing hint is the pricing tag.

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.