Skip to main content
Glama

Starfile

Has this product or company been recalled?

search_recalls
Read-onlyIdempotent

Search U.S. recalls by product words and/or company: FDA food, drug and medical-device recalls (enforcement reports) and CPSC consumer-product recalls. Returns matching recalls newest first with class, reason, status and dates, the total number on record, and the firms with the most matches. Pass recall_id to get one recall.

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": "search_recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoCompany name, e.g. "Acme Foods".
typeNofood, drug, device (FDA) or product (CPSC). Default all.
limitNoMax results (default 10, max 25).
queryNoProduct words, e.g. "peanut butter", "infusion pump", "baby crib".
sinceNoOnly recalls initiated on or after this date (YYYY-MM-DD).
untilNoOnly recalls initiated on or before this date (YYYY-MM-DD).
class_iNoOnly Class I (the most serious FDA class).
recall_idNoOne recall by its number (e.g. F-0123-2025, Z-0456-2024, D-0789-2023, or a CPSC number).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/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 genuinely new context: results are ordered newest-first, include class, reason, status and dates, plus an aggregate total and top matching firms — valuable because there is no output schema.

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?

Three tight sentences, front-loaded with scope and sources, then return shape, then the single-recall mode. No filler or restated title.

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?

For an 8-parameter, all-optional read-only search with no output schema, the description covers scope, source coverage, filtering semantics, result ordering and returned fields. Nothing an agent needs to call it correctly is left unstated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the and/or relationship between query and firm, the newest-first ordering tied to the date filters, and the dual mode implied by recall_id.

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?

Names a specific verb and resource plus its data sources (FDA food/drug/device enforcement reports and CPSC consumer-product recalls). It also states the lookup-by-ID mode, so an agent can tell exactly what corpus this tool covers.

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?

Gives clear operative guidance: combine product words 'and/or' company, and pass recall_id for a single recall. It stops short of stating when NOT to use it or naming an alternative, but no sibling in the provided list covers recalls, so the routing risk is low.

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