Recall Check

Search pet food recalls

search_pet_food_recalls

Read-onlyIdempotent

Use this when the user asks about a recall of dog food, cat food, pet treats or other pet food, such as "dog food recall this week". Optionally pass a brand or hazard as query, and set withinDays for recent recalls, such as 7 for this week. Returns matching FDA recall announcements, newest first, with the title, date, summary and FDA link. It only sees the FDA's 20 most recent recall announcements (about three weeks) and says so, so for an older recall point the user to the FDA recalls page.

Input Schema

Name	Required	Description
`limit`	No	Most recalls to return, newest first (default 5)
`query`	No	Optional brand or hazard to look for, such as "Purina" or "salmonella"; leave out to list every recent pet food recall
`withinDays`	No	Only announcements from the last this many days, such as 7 for this week

Output Schema

Name	Required	Description	Default
`query`	No
`notice`	Yes
`status`	Yes
`matches`	No
`message`	No
`recalls`	No
`coveredFrom`	No
`moreAvailable`	No
`otherPetFoodRecalls`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

Changed1 schema field changedOct 4, 2026
- addedOutput schema / properties / otherPetFoodRecalls
```
Added value: +{
+  "type": "integer"
+}
```
Changed1 schema field changedOct 4, 2026
- removedOutput schema / properties / otherPetFoodRecalls
```
Removed value: -{
-  "type": "integer"
-}
```
First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so safety is covered. The description adds genuinely useful context beyond that: the tool only sees the FDA's 20 most recent announcements (~3 weeks), it discloses this limitation to the user, and results are ordered newest first. Return-field detail is partly redundant with the 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.

Conciseness4/5

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

Three sentences, front-loaded with the trigger condition, then parameters, then return shape and the coverage limitation. Every sentence carries information, though the return-field sentence overlaps with the output schema.

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 a three-optional-param search tool with full schema coverage, annotations and an output schema, the description covers trigger, parameter intent, ordering, result contents and the critical data-window limitation. Nothing needed to call it correctly is missing.

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 and withinDays including their examples and bounds. The description restates the query and withinDays intent ('pass a brand or hazard', '7 for this week') but adds no syntax or format information the schema lacks, so the baseline 3 applies.

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 gives a specific verb+resource (search FDA pet food recall announcements) and scopes it tightly to dog food, cat food, pet treats and other pet food, which cleanly separates it from siblings like search_food_drug_recalls and search_product_recalls.

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 states exactly when to invoke (user asks about a pet food recall) with a sample utterance, explains how the optional parameters change behavior, and names a when-not/fallback case: for recalls older than the ~3-week FDA window, point the user to the FDA recalls page.

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

All Recall Check tools Inspect

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.