Skip to main content
Glama

cpsc-recalls-mcp-server

by io.github.cyanheads

Get Recent CPSC Recalls

cpsc_get_recent
Read-only

Fetch the most recent CPSC consumer product recalls, ordered newest-first. Use for "what's been recalled lately?" or a product safety feed. Always applies a date window (default: last 30 days) — without a date filter the API returns all 9,800+ records. Page past limit with offset: narrowing days cannot page, because the window is anchored to today and shrinking it drops the oldest records rather than advancing past the newest. CPSC jurisdiction: consumer products only — food, vehicles, drugs, and pesticides are covered by other agencies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLook back this many days from today. Defaults to 30. Use 7 for a weekly digest, 90 for a quarterly review.
limitNoMaximum number of recalls to return. Defaults to 20.
offsetNoSkip this many recalls in the window before returning results. Combine with limit to page through total_found — e.g. limit 20 with offset 0, 20, 40. An offset at or past total_found returns an empty result set rather than an error.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
offsetNoNumber of recalls skipped before this window.
periodNoDate range queried.
recallsNoRecent recalls, newest-first.
has_moreNoTrue when recalls remain past this window — call again with offset raised by the number of recalls returned.
truncatedNoTrue when total_found exceeds the limit. Independent of offset.
source_noteNoProvenance caveat: recall fields are relayed from CPSC unedited and unverified; check cpsc_url before a consumer-facing decision.
total_foundNoTotal recalls in this period, counted before offset and limit narrow the window.
cpsc_jurisdictionNoCPSC covers consumer products — toys, electronics, furniture, appliances, tools, clothing. Does NOT cover: food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), pesticides (EPA), firearms (ATF).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "recalls",
+      "period",
+      "total_found",
+      "truncated",
+      "offset",
+      "has_more",
+      "cpsc_jurisdiction",
+      "source_note"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
    • addedOutput schema / properties / error
      Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `upstream_error`: The saferproducts.gov API returned a transient error or timed out `upstream_rejected`: The saferproducts.gov API answered with an error row instead of recall records, which the same request will always produce Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "upstream_error",
+            "upstream_rejected"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
    • removedOutput schema / required
      Removed value: -[
-  "recalls",
-  "period",
-  "total_found",
-  "truncated",
-  "offset",
-  "has_more",
-  "cpsc_jurisdiction",
-  "source_note"
-]
  2. Changed7 schema fields changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many recalls in the window before returning results. Combine with limit to page through total_found — e.g. limit 20 with offset 0, 20, 40. An offset at or past total_found returns an empty result set rather than an error.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / has_more
      Added value: +{
+  "description": "True when recalls remain past this window — call again with offset raised by the number of recalls returned.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / offset
      Added value: +{
+  "description": "Number of recalls skipped before this window.",
+  "type": "number"
+}
    • changedOutput schema / properties / recalls / items / properties / remedy_options / description
      Previous value: -"Remedy types."New value: +"Remedy types: Refund, Repair, Replace, New Instructions, Dispose, Label, No Remedy Available, Inspect. Multiple may apply. Often empty — CPSC classified the remedy on fewer than half its records; call cpsc_get_recall for the remedy narrative when this is empty."
    • changedOutput schema / properties / total_found / description
      Previous value: -"Total recalls in this period before the limit was applied."New value: +"Total recalls in this period, counted before offset and limit narrow the window."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when total_found exceeds the limit."New value: +"True when total_found exceeds the limit. Independent of offset."
    • changedOutput schema / required
      Previous value: -[
-  "recalls",
-  "period",
-  "total_found",
-  "truncated",
-  "cpsc_jurisdiction",
-  "source_note"
-]New value: +[
+  "recalls",
+  "period",
+  "total_found",
+  "truncated",
+  "offset",
+  "has_more",
+  "cpsc_jurisdiction",
+  "source_note"
+]
  3. Changed4 schema fields changed
    • addedOutput schema / properties / recalls / items / properties / data_quality_notes
      Added value: +{
+  "description": "Gaps this server observed in the upstream CPSC record — absent hazard text, absent product entries. Derived from which fields CPSC left empty, not from any judgement about the recall itself. Empty when nothing is missing.",
+  "items": {
+    "description": "One gap found in the upstream record.",
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / recalls / items / required
      Previous value: -[
-  "recall_number",
-  "recall_date",
-  "title",
-  "hazards",
-  "remedy_options",
-  "products",
-  "cpsc_url"
-]New value: +[
+  "recall_number",
+  "recall_date",
+  "title",
+  "hazards",
+  "remedy_options",
+  "products",
+  "cpsc_url",
+  "data_quality_notes"
+]
    • addedOutput schema / properties / source_note
      Added value: +{
+  "description": "Provenance caveat: recall fields are relayed from CPSC unedited and unverified; check cpsc_url before a consumer-facing decision.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "recalls",
-  "period",
-  "total_found",
-  "truncated",
-  "cpsc_jurisdiction"
-]New value: +[
+  "recalls",
+  "period",
+  "total_found",
+  "truncated",
+  "cpsc_jurisdiction",
+  "source_note"
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by explaining that the tool always applies a date window, warns that without a filter it returns 9,800+ records, details the paging limitation that shrinking the window drops oldest records, and clarifies CPSC jurisdiction. This is rich behavioral context that prevents misuse and sets accurate expectations. No contradiction with annotations.

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?

The description is front-loaded with the core purpose, then usage guidance, then the crucial date-window and paging caveats, and finally jurisdiction. Every sentence carries essential information—no filler or redundancy. The structure guides the agent from what the tool does to how to use it safely.

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?

The description covers all operational aspects for correct invocation: ordering, date window behavior, paging caveats, and jurisdiction boundaries. The output schema is present, so return format is covered. An agent can confidently call this tool without missing critical constraints.

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% with detailed descriptions for all three parameters. The description adds critical semantic context: the consequence of not filtering (all 9,800+ records) and the subtle paging behavior that narrowing the days window cannot advance pages. This goes beyond the schema's static definitions, though the schema already documents offset behavior.

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 states the verb 'Fetch', the resource 'most recent CPSC consumer product recalls', and the ordering 'newest-first'. It clearly distinguishes this tool as a recency-focused listing, which is distinct from fetching a specific recall or searching. The purpose is unambiguous and immediately actionable.

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?

The description explicitly says to use it for 'what's been recalled lately?' or a product safety feed, providing clear context for when to choose this tool. It does not name sibling tools or mention when not to use it, but the guidance is direct enough for an agent to correctly identify this as the go-to for recent recalls.

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

All cpsc-recalls-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search for recalls, fetch recent recalls, and get full details by recall number. There is no overlap in functionality, and the descriptions reinforce when to use each.

Naming Consistency5/5

All tool names follow the cpsc_ prefix with a verb_noun pattern (get_recall, get_recent, search_recalls). The naming is perfectly consistent and predictable.

Tool Count5/5

Three tools is a well-scoped set for a recall lookup server. Each tool serves a necessary role (search, recent, detail) with no redundant or missing core operations.

Completeness5/5

The tool set covers the full read-only lifecycle for CPSC recalls: searching, browsing recent, and retrieving detailed records. All necessary operations for the domain are present, with no obvious gaps.

Resources