Recall Canary

Get one recall by agency and slug

get_recall

Read-only

Fetch the full Recall Canary record for a single U.S. federal recall, given the agency and slug returned by search_recalls. Includes the hazard description, the affected product list with lot codes and UPCs, the recommended consumer action, distribution, the agency source link, and the firm slug (firm.slug, with firm.page_url when the firm has a page) for search_recalls' firm filter. Also resolves preliminary agency press releases: an orphan, or a linked one that kept its own URL (its recalls in linked_recalls). Read-only.

Input Schema

Name	Required	Description	Default
`slug`	Yes	The record slug from its URL, e.g. "acme-foods-peanut-butter". The 26-character ULID id is also accepted and resolves to what its URL shows (for a matched press release, often its recall).
`agency`	Yes	Lowercase agency segment from the record URL. Part of the lookup key, not decoration: a correct slug under the wrong agency is a miss.

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`firm`	No
`risk`	No	The agency rating as the page shows it (for example "High risk" for an FDA Class I recall). Null where the page shows no risk line.
`slug`	No
`dates`	No
`notes`	Yes	Caveats for this record, including the aggregator-lag and not-a-clearance statement.
`title`	Yes	Agency-published title. Never model-written.
`agency`	Yes	Known values: FDA, FDA_IRES, FSIS, CPSC, NHTSA, ADMIN.
`reason`	No	The agency's own stated reason, not model-written.
`status`	No
`license`	Yes	Attribution and terms (DATA-LICENSE).
`related`	No
`category`	No	Known values: FOOD, DRUG, DEVICE, COSMETIC, CONSUMER_PRODUCT, VEHICLE, AUTO_EQUIPMENT.
`html_url`	Yes	Absolute URL of the human-readable page.
`products`	No
`severity`	No	Known values: CRITICAL, MODERATE, LOW.
`timeline`	No	Dated steps of the record, in date order. Each step names who acted on that date.
`canonical`	Yes	Absolute URL of this representation.
`firm_name`	No
`listed_at`	No	Since api 2.6.0. The date the listing shows and sorts by; equals this record's search_recalls row. A recall's listing date is in dates.listed_at.
`source_url`	No	The agency's own notice.
`api_version`	Yes
`description`	No	Full agency description. FSIS: sanitized HTML; others: plain text. Sanitize or escape before display.
`hazard_tags`	Yes
`record_type`	Yes
`snapshot_at`	Yes	ISO-8601 UTC response-generation time, second precision. First key on purpose.
`advisory_url`	No
`ai_generated`	Yes	Provenance: true where the field holds model-written text. Over-attributes on purpose.
`distribution`	No
`published_at`	No	Deprecated: the stored pub_date.
`display_title`	No
`mcp_truncated`	No	Present only when a long list was cut to 25 for this response.
`product_count`	No	The true event scope, which may exceed products.length.
`story_lead_id`	No	Set on a later record of a recall story; the lead it belongs to.
`critical_flags`	No	NHTSA-only in practice. An absent key means the agency did not state the flag. null for a withdrawn (RETRACTED) record.
`identification`	Yes	Page-derived identification: the products and codes the record names. Not a completeness guarantee; `partial` says when the list is incomplete, including when this response cut `products` to 25 (`mcp_truncated.identification_products`).
`linked_recalls`	No
`press_releases`	No
`story_lead_url`	No
`units_affected`	No
`consumer_action`	No	The "What to do" text. Null on a withdrawn alert.
`display_summary`	No
`source_recall_id`	No	Agency key; a CPSC one can be stale.
`content_changed_at`	Yes	When the published content last changed.
`products_truncated`	No	True when `product_count` exceeds the length of `products`
`agency_published_at`	No
`company_announced_at`	No
`company_product_list`	No	The company's own list of the affected products, when the agency notice points to it instead of naming them. A product missing from `identification` may still be recalled: check this list.
`display_summary_short`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / properties / identification / description

Previous value: -"Page-derived identification: the products and codes the record names. Not a completeness guarantee; `partial` says when the list is incomplete."New value: +"Page-derived identification: the products and codes the record names. Not a completeness guarantee; `partial` says when the list is incomplete, including when this response cut `products` to 25 (`mcp_truncated.identification_products`)."

First observedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description restates "Read-only" but adds real substance: what the payload contains (hazard, lot codes/UPCs, consumer action, distribution, source link), the firm.slug/page_url exposure for the sibling's firm filter, and the orphan/linked-press-release edge case. That edge-case disclosure is genuine behavioral context an agent could not infer from the 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?

Two sentences, front-loaded with the core action, then the payload inventory and edge cases. The field enumeration is long but each item (lot codes, UPCs, firm.slug for the firm filter) conveys something an agent would otherwise have to discover empirically.

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?

Output schema exists, so return values need no formal explanation, yet the description still summarizes the shape and explicitly covers the tricky press-release path. Combined with the 100% schema coverage and read-only annotation, nothing an agent needs to invoke this 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 coverage is 100% and the schema itself already explains the ULID acceptance, max length, and the agency enum's role as part of the lookup key. The description adds only provenance (both values come from search_recalls), 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?

States a specific verb and resource ("Fetch the full Recall Canary record for a single U.S. federal recall") and pins the lookup key to agency + slug returned by search_recalls. An agent can immediately distinguish detail-fetch from the sibling search tool.

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?

Clearly establishes the follow-up pattern: call this with the agency and slug that search_recalls returned. It also notes the press-release resolution case, which tells the agent why a lookup might return a related recall. There is no explicit when-not, but the workflow context is unambiguous.

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

All Recall Canary 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.

Resources

Need Help?