Recall Check

Search product recalls

search_product_recalls

Read-onlyIdempotent

Use this when the user asks whether a consumer product is recalled, such as a crib, stroller, toy, appliance, heater or tool, or "is this car seat recalled?" (for car seat accessories). Pass the brand and product as on the label. Returns matching U.S. Consumer Product Safety Commission recalls, newest first, with the hazard, the remedy, the company contact and the CPSC link. Set withinDays for recent recalls only. Car seats and tires themselves are NHTSA recalls this tool cannot see, and the answer says so. It does not cover vehicles, food or drugs.

Input Schema

Name	Required	Description
`limit`	No	Most recalls to return, newest first (default 5)
`query`	Yes	Brand and product as on the label, such as "Graco car seat" or "Fisher-Price sleeper"
`withinDays`	No	Only recalls announced in the last this many days, such as 7 for this week

Output Schema

Name	Required	Description	Default
`query`	Yes
`notice`	Yes
`status`	Yes
`matches`	No
`message`	No
`recalls`	No
`moreAvailable`	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"
+}

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 readOnly/idempotent/openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: results are newest-first, each carries hazard, remedy, company contact and CPSC link, and the tool discloses its own coverage gap ('the answer says so'). It stops short of pagination/rate-limit detail, but the bar is lower with annotations present.

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?

Front-loads the triggering scenario, then scope, return shape and exclusions in a compact run of clauses. Dense but every sentence earns its place; only the query-formatting sentence mildly duplicates the 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?

Despite an output schema, the description goes further by naming the returned fields and, critically, the domains it cannot see and that the answer surfaces that limitation. For a scope-bounded search tool this leaves nothing an agent needs to call 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 the baseline is 3. The description restates the schema's own query guidance ('brand and product as on the label') and lightly contextualizes withinDays ('for recent recalls only'), adding marginal meaning rather than new syntax or format detail.

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 and resource (search U.S. CPSC consumer product recalls) and explicitly bounds the scope against siblings: 'does not cover vehicles, food or drugs' and car seats/tires are NHTSA recalls this tool cannot see. An agent can distinguish it from check_vehicle_recalls, search_food_drug_recalls and search_pet_food_recalls without opening a schema.

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?

Names the triggering user question ('is this car seat recalled?') and the artifact to pass ('brand and product as on the label'), plus explicit exclusions and the alternative source (NHTSA) for out-of-scope items. Both when-to-use and when-not-to-use are covered.

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.