Skip to main content
Glama

FDA Recall Alerts — Food & Product Safety (fdarecall)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: fdarecall: FDA recall enforcement database (food, drug, device). Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the newest FDA recalls this week?; Which Class I recalls are currently ongoing?. FREE preview — no key, no payment. Try one of the sample questions now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context — no API key, no payment, and a 20-queries/session cap — but that cap and the 0.01 USDC price describe the paid listing query, not the preview, which risks conflating the free preview with a paid call. It also omits what the preview actually returns.

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

Conciseness3/5

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

The key point (free, no key) is front-loaded and the sample questions are genuinely useful for usage. But the checkmark emoji, pricing line, and trailing marketing call-to-action are promotional filler that dilute an otherwise short definition and sit oddly in a tool description.

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?

This is a simple, zero-required-parameter read tool with full schema coverage and a complete annotation set, so the bar is low. Still, an agent cannot tell from the description alone that the response is limited to public metadata rather than actual recall results, which is the one fact that matters most for calling it 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%, so both optional parameters (slug and question) are fully documented in the schema. The description adds nothing about either parameter — no explanation of how the question is used or when slug is required versus defaulted — so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the underlying resource ("fdarecall: FDA recall enforcement database (food, drug, device)") and calls itself a "FREE preview," but it never plainly states what the tool itself returns. The clearest statement of purpose ("Free, guest-callable taste of a listing (public metadata only)") lives in the schema description, not the tool description, so an agent must read structured fields to learn the actual output.

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?

It gives sample questions and an explicit "try one now" nudge, and the no-key/no-payment framing implies this is the zero-cost entry point before paid queries. However, it never names or contrasts with siblings such as data_session_query or data_session_open, and gives no when-not guidance (e.g., that the preview returns metadata only and not real query results).

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