Skip to main content
Glama

search_product_recalls

Read-onlyIdempotent

Search product recalls by query. Query uses websearch syntax: unquoted words are AND, OR is or, -term excludes, quoted phrases match as a unit (example: Generac Generator -Portable). Optional filters: source (cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, canada, openfda), since/until (YYYY-MM-DD), location (country, region, or place, ANDed with the query), offset, limit. Descriptions are truncated and extracted products are capped; use get_product_recall for the full text.

Input Schema

NameRequiredDescriptionDefault
limitNonumber of recalls to return, 1-100, default 3
queryNowebsearch query: unquoted words are AND, OR is or, -term excludes, quoted phrases match as a unit. Example: Generac Generator -Portable
sinceNooptional published-on start date YYYY-MM-DD
untilNooptional published-on end date YYYY-MM-DD
yearsNooptional published window in years (1-50). Ignored when since is set
offsetNonumber of recalls to skip
sourceNooptional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, canada, or openfda. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; healthcanada, cfia, and hc-sc map to canada; enforcement, res, and fdaenforcement map to openfda. For more than one source, pass sources.
sourcesNooptional sources to include (OR). Same values as source
locationNooptional country, region, or place; ANDed with the query. USA, Canada, Mexico, EU, and Europe match places in that region. CA is California, not Canada.

Output Schema

NameRequiredDescriptionDefault
offsetYes
recallsYes
nextOffsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "cpsc",
      -  "fdafoodsafety",
      -  "FDAMedWatch",
      -  "usda",
      -  "nhtsa",
      -  "canada",
      -  "costco",
      -  "target",
      -  "walmart",
      -  "openfda"
      -]New value: +[
      +  "cpsc",
      +  "fdafoodsafety",
      +  "FDAMedWatch",
      +  "usda",
      +  "nhtsa",
      +  "canada",
      +  "openfda"
      +]
    • changedInput schema / properties / sources / items / enum
      Previous value: -[
      -  "cpsc",
      -  "fdafoodsafety",
      -  "FDAMedWatch",
      -  "usda",
      -  "nhtsa",
      -  "canada",
      -  "costco",
      -  "target",
      -  "walmart",
      -  "openfda"
      -]New value: +[
      +  "cpsc",
      +  "fdafoodsafety",
      +  "FDAMedWatch",
      +  "usda",
      +  "nhtsa",
      +  "canada",
      +  "openfda"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, canada, costco, target, walmart, or openfda. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; healthcanada, cfia, and hc-sc map to canada; sams maps to walmart; enforcement, res, and fdaenforcement map to openfda. For more than one source, pass sources."New value: +"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, canada, or openfda. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; healthcanada, cfia, and hc-sc map to canada; enforcement, res, and fdaenforcement map to openfda. For more than one source, pass sources."
  3. Changed3 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, costco, target, walmart, or openfda. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; sams maps to walmart; enforcement, res, and fdaenforcement map to openfda. For more than one source, pass sources."New value: +"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, canada, costco, target, walmart, or openfda. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; healthcanada, cfia, and hc-sc map to canada; sams maps to walmart; enforcement, res, and fdaenforcement map to openfda. For more than one source, pass sources."
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "cpsc",
      -  "fdafoodsafety",
      -  "FDAMedWatch",
      -  "usda",
      -  "nhtsa",
      -  "costco",
      -  "target",
      -  "walmart",
      -  "openfda"
      -]New value: +[
      +  "cpsc",
      +  "fdafoodsafety",
      +  "FDAMedWatch",
      +  "usda",
      +  "nhtsa",
      +  "canada",
      +  "costco",
      +  "target",
      +  "walmart",
      +  "openfda"
      +]
    • changedInput schema / properties / sources / items / enum
      Previous value: -[
      -  "cpsc",
      -  "fdafoodsafety",
      -  "FDAMedWatch",
      -  "usda",
      -  "nhtsa",
      -  "costco",
      -  "target",
      -  "walmart",
      -  "openfda"
      -]New value: +[
      +  "cpsc",
      +  "fdafoodsafety",
      +  "FDAMedWatch",
      +  "usda",
      +  "nhtsa",
      +  "canada",
      +  "costco",
      +  "target",
      +  "walmart",
      +  "openfda"
      +]
  4. Changed4 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"optional country, region, or place; ANDed with the query. US aliases such as CA and California still apply"New value: +"optional country, region, or place; ANDed with the query. USA, Canada, Mexico, EU, and Europe match places in that region. CA is California, not Canada."
    • changedInput schema / properties / source / description
      Previous value: -"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, costco, target, or walmart. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; sams maps to walmart. For more than one source, pass sources."New value: +"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, costco, target, walmart, or openfda. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; sams maps to walmart; enforcement, res, and fdaenforcement map to openfda. For more than one source, pass sources."
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "cpsc",
      -  "fdafoodsafety",
      -  "FDAMedWatch",
      -  "usda",
      -  "nhtsa",
      -  "costco",
      -  "target",
      -  "walmart"
      -]New value: +[
      +  "cpsc",
      +  "fdafoodsafety",
      +  "FDAMedWatch",
      +  "usda",
      +  "nhtsa",
      +  "costco",
      +  "target",
      +  "walmart",
      +  "openfda"
      +]
    • changedInput schema / properties / sources / items / enum
      Previous value: -[
      -  "cpsc",
      -  "fdafoodsafety",
      -  "FDAMedWatch",
      -  "usda",
      -  "nhtsa",
      -  "costco",
      -  "target",
      -  "walmart"
      -]New value: +[
      +  "cpsc",
      +  "fdafoodsafety",
      +  "FDAMedWatch",
      +  "usda",
      +  "nhtsa",
      +  "costco",
      +  "target",
      +  "walmart",
      +  "openfda"
      +]
  5. Changed3 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, costco, target, or walmart. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; sams maps to walmart."New value: +"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, costco, target, or walmart. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; sams maps to walmart. For more than one source, pass sources."
    • addedInput schema / properties / sources
      Added value: +{
      +  "description": "optional sources to include (OR). Same values as source",
      +  "items": {
      +    "enum": [
      +      "cpsc",
      +      "fdafoodsafety",
      +      "FDAMedWatch",
      +      "usda",
      +      "nhtsa",
      +      "costco",
      +      "target",
      +      "walmart"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array",
      +  "uniqueItems": true
      +}
    • addedInput schema / properties / years
      Added value: +{
      +  "description": "optional published window in years (1-50). Ignored when since is set",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  6. Changed2 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, or usda. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch."New value: +"optional source filter: cpsc, fdafoodsafety, FDAMedWatch, usda, nhtsa, costco, target, or walmart. Aliases: FDA and food map to fdafoodsafety; medwatch maps to FDAMedWatch; vehicle, vin, and car map to nhtsa; sams maps to walmart."
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "cpsc",
      -  "fdafoodsafety",
      -  "FDAMedWatch",
      -  "usda"
      -]New value: +[
      +  "cpsc",
      +  "fdafoodsafety",
      +  "FDAMedWatch",
      +  "usda",
      +  "nhtsa",
      +  "costco",
      +  "target",
      +  "walmart"
      +]
  7. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, so the bar is lower; the description still adds real value by disclosing that descriptions are truncated and extracted products are capped, plus a default limit of 3 and how location is ANDed. It does not mention rate limits or result ordering, which keeps it below a 5.

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?

Two sentences, front-loaded with purpose then query syntax then filters then the truncation caveat. Dense but every clause carries information; the filter list is a little run-on but still readable.

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 an output schema, full annotation coverage and 100% schema descriptions, the description only needs to cover scope and caveats — which it does via truncation and the get_product_recall pointer. The omission of the 'years' parameter keeps it short of complete.

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 coverage is 100% and each parameter is documented there, including the query syntax and source aliases, so the description largely restates the schema. It omits the 'years' parameter entirely, and its enumerations of sources duplicate the enum. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('Search product recalls by query') and immediately distinguishes itself from the sibling get_product_recall by explaining that results are truncated and the sibling returns the full text. An agent can route between the two without opening any schema.

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?

Explicitly names the alternative (get_product_recall) and the condition that selects it (need full text / extracted products). Lacks guidance on when to prefer the UPC or image search siblings, but the core search-vs-fetch split is clear.

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