Skip to main content
Glama

cpsc-recalls-mcp-server

Get CPSC Recall Detail

cpsc_get_recall
Read-onlyIdempotent

Fetch the full record for one CPSC recall by recall number: hazard description, remedy instructions, every product variant, UPCs, incident and injury reports, images, and the official CPSC recall page URL. Get a recall number from cpsc_search_recalls or cpsc_get_recent. CPSC jurisdiction: consumer products, including child-resistant packaging for drugs and supplements, ATVs and snowmobiles, bicycle tires, and gun safes and locks; food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), and firearms (ATF) belong to other agencies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recall_number": "<recall_number>"
    },
    "name": "cpsc_get_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
recall_numberYesCPSC recall number: 5 digits, e.g. "25043", with a letter a–d on some 1998–2001 records, e.g. "99003a". Get one from cpsc_search_recalls or cpsc_get_recent results.

Output Schema

NameRequiredDescriptionDefault
upcsNoUPC codes for this recall (sparse — ~4% of records have UPCs). CPSC lists UPCs for the recall as a whole, not per product, so on a recall covering several products a UPC cannot be tied to one of them.
errorNoPresent when the call failed. Absent on success.
titleNoOfficial recall title.
imagesNoProduct and identification images from the recall notice.
hazardsNoHazards — read this first.
cpsc_urlNoOfficial CPSC recall page — authoritative source for consumers.
injuriesNoInjury and incident report narrative, e.g. "None reported" or incident count.
productsNoProducts covered. A recall may include multiple products. Model numbers are often in the description text, not a structured field.
importersNoImporter company names.
retailersNoRetailer names with sale date ranges and price.
descriptionNoFull recall description including product identification details. Model numbers are typically embedded here, not in a structured field. Null when CPSC published the record without a description — rare, but a genuine record can still be complete otherwise.
recall_dateNoDate issued, ISO 8601.
source_noteNoProvenance caveat: recall fields are CPSC record text with HTML markup and character codes converted to plain text, not otherwise edited or verified; check cpsc_url before a consumer-facing decision.
distributorsNoDistributor company names.
last_updatedNoDate last published, ISO 8601.
manufacturersNoManufacturer names (often empty — see importers).
recall_numberNoRecall identifier.
remedy_optionsNoRemedy types available: Refund, Repair, Replace, New Instructions, Dispose, Label, No Remedy Available, Inspect. Often empty — CPSC classified the remedy on fewer than half its records. Read remedy_instructions when this is empty, and fall back to cpsc_url when that is empty too, rather than reporting that no remedy exists.
consumer_contactNoContact information for claiming the remedy. Null when not provided.
cpsc_jurisdictionNoWhich products CPSC covers, including those near the lines of other agencies, and which agencies own food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), and firearms (ATF).
data_quality_notesNoGaps this server observed in the CPSC record — absent description, 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.
coordinated_recallsNoURLs of coordinated recalls by other agencies (e.g., Canada Health).
remedy_instructionsNoFull remedy instructions — exactly what a consumer should do and how to claim.
manufacturer_countriesNoCountries of manufacture.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / recall_number / description
      Previous value: -"CPSC recall number: 5 digits for 2002–present records, e.g. \"25043\", or 5 digits plus a letter a–d for 1998–2001 records, e.g. \"99003a\". Get one from cpsc_search_recalls or cpsc_get_recent results."New value: +"CPSC recall number: 5 digits, e.g. \"25043\", with a letter a–d on some 1998–2001 records, e.g. \"99003a\". Get one from cpsc_search_recalls or cpsc_get_recent results."
    • changedOutput schema / properties / cpsc_jurisdiction / description
      Previous value: -"Which products CPSC covers and which agencies cover the rest — food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), pesticides (EPA), firearms (ATF)."New value: +"Which products CPSC covers, including those near the lines of other agencies, and which agencies own food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), and firearms (ATF)."
  2. Changed2 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No recall exists with the given recall number. `upstream_error`: The CPSC recall service (saferproducts.gov) was unavailable, timed out, or sent an unreadable response. `upstream_rejected`: CPSC rejected the lookup instead of returning a recall, and it rejects the same request every time. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No recall exists with the given recall number. `upstream_error`: The CPSC recall service (saferproducts.gov) was unavailable, timed out, reported a temporary failure reading its recall data, or sent an unreadable response. `upstream_rejected`: CPSC rejected the lookup instead of returning a recall, and it rejects the same request every time. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / source_note / description
      Previous value: -"Provenance caveat: recall fields are relayed from CPSC unedited and unverified; check cpsc_url before a consumer-facing decision."New value: +"Provenance caveat: recall fields are CPSC record text with HTML markup and character codes converted to plain text, not otherwise edited or verified; check cpsc_url before a consumer-facing decision."
  3. Changed7 schema fields changed
    • changedInput schema / properties / recall_number / description
      Previous value: -"CPSC recall number. Modern records (2002–present) are 5-digit numeric, e.g. \"25043\". Historical records from 1998–2001 may have a letter suffix a–d, e.g. \"99003a\". Obtain from cpsc_search_recalls results."New value: +"CPSC recall number: 5 digits for 2002–present records, e.g. \"25043\", or 5 digits plus a letter a–d for 1998–2001 records, e.g. \"99003a\". Get one from cpsc_search_recalls or cpsc_get_recent results."
    • changedOutput schema / properties / cpsc_jurisdiction / description
      Previous value: -"CPSC 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)."New value: +"Which products CPSC covers and which agencies cover the rest — food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), pesticides (EPA), firearms (ATF)."
    • changedOutput schema / properties / data_quality_notes / description
      Previous value: -"Gaps this server observed in the upstream CPSC record — absent description, 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."New value: +"Gaps this server observed in the CPSC record — absent description, 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."
    • changedOutput schema / properties / data_quality_notes / items / description
      Previous value: -"One gap found in the upstream record."New value: +"One gap found in the CPSC record."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No recall exists with the given recall number. `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 a recall record, which the same request will always produce. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No recall exists with the given recall number. `upstream_error`: The CPSC recall service (saferproducts.gov) was unavailable, timed out, or sent an unreadable response. `upstream_rejected`: CPSC rejected the lookup instead of returning a recall, and it rejects the same request every time. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / products / description
      Previous value: -"Products covered. A recall may include multiple products. Note: model numbers are often in the description text, not a structured field."New value: +"Products covered. A recall may include multiple products. Model numbers are often in the description text, not a structured field."
    • changedOutput schema / properties / upcs / description
      Previous value: -"UPC codes for this recall (sparse — ~4% of records have UPCs). UPCs are stored at the recall level in the API, not per-product; when the recall covers multiple products, UPC-to-product attribution is ambiguous."New value: +"UPC codes for this recall (sparse — ~4% of records have UPCs). CPSC lists UPCs for the recall as a whole, not per product, so on a recall covering several products a UPC cannot be tied to one of them."
  4. Changed5 schema fields changed
    • removedOutput schema / properties / consumer_contact / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / consumer_contact / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No recall exists with the given recall number `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 a recall record, which the same request will always produce Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No recall exists with the given recall number. `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 a recall record, which the same request will always produce. Other values are possible when a failure originates below the handler."
  5. 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": [
      +      "recall_number",
      +      "recall_date",
      +      "last_updated",
      +      "title",
      +      "description",
      +      "cpsc_url",
      +      "consumer_contact",
      +      "hazards",
      +      "remedy_options",
      +      "remedy_instructions",
      +      "products",
      +      "upcs",
      +      "injuries",
      +      "manufacturers",
      +      "importers",
      +      "retailers",
      +      "distributors",
      +      "manufacturer_countries",
      +      "images",
      +      "coordinated_recalls",
      +      "data_quality_notes",
      +      "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: `not_found`: No recall exists with the given recall number `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 a recall record, which the same request will always produce Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "not_found",
      +            "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: -[
      -  "recall_number",
      -  "recall_date",
      -  "last_updated",
      -  "title",
      -  "description",
      -  "cpsc_url",
      -  "consumer_contact",
      -  "hazards",
      -  "remedy_options",
      -  "remedy_instructions",
      -  "products",
      -  "upcs",
      -  "injuries",
      -  "manufacturers",
      -  "importers",
      -  "retailers",
      -  "distributors",
      -  "manufacturer_countries",
      -  "images",
      -  "coordinated_recalls",
      -  "data_quality_notes",
      -  "cpsc_jurisdiction",
      -  "source_note"
      -]
  6. Changed1 schema field changed
    • changedOutput schema / properties / remedy_options / description
      Previous value: -"Remedy types available: Refund, Repair, Replace, Dispose, Label, New Instructions."New value: +"Remedy types available: Refund, Repair, Replace, New Instructions, Dispose, Label, No Remedy Available, Inspect. Often empty — CPSC classified the remedy on fewer than half its records. Read remedy_instructions when this is empty, and fall back to cpsc_url when that is empty too, rather than reporting that no remedy exists."
  7. Changed6 schema fields changed
    • addedOutput schema / properties / data_quality_notes
      Added value: +{
      +  "description": "Gaps this server observed in the upstream CPSC record — absent description, 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"
      +}
    • addedOutput schema / properties / description / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / description / description
      Previous value: -"Full recall description including product identification details. Model numbers are typically embedded here, not in a structured field."New value: +"Full recall description including product identification details. Model numbers are typically embedded here, not in a structured field. Null when CPSC published the record without a description — rare, but a genuine record can still be complete otherwise."
    • removedOutput schema / properties / description / type
      Removed value: -"string"
    • 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: -[
      -  "recall_number",
      -  "recall_date",
      -  "last_updated",
      -  "title",
      -  "description",
      -  "cpsc_url",
      -  "consumer_contact",
      -  "hazards",
      -  "remedy_options",
      -  "remedy_instructions",
      -  "products",
      -  "upcs",
      -  "injuries",
      -  "manufacturers",
      -  "importers",
      -  "retailers",
      -  "distributors",
      -  "manufacturer_countries",
      -  "images",
      -  "coordinated_recalls",
      -  "cpsc_jurisdiction"
      -]New value: +[
      +  "recall_number",
      +  "recall_date",
      +  "last_updated",
      +  "title",
      +  "description",
      +  "cpsc_url",
      +  "consumer_contact",
      +  "hazards",
      +  "remedy_options",
      +  "remedy_instructions",
      +  "products",
      +  "upcs",
      +  "injuries",
      +  "manufacturers",
      +  "importers",
      +  "retailers",
      +  "distributors",
      +  "manufacturer_countries",
      +  "images",
      +  "coordinated_recalls",
      +  "data_quality_notes",
      +  "cpsc_jurisdiction",
      +  "source_note"
      +]
  8. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds jurisdiction boundaries and signals the record is exhaustive ('every product variant, UPCs, incident and injury reports'), but says nothing about what happens for an invalid or unknown recall number, or whether the official CPSC URL is always 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-loaded with the core action and return contents, then sourcing, then jurisdiction. The jurisdiction sentence is long but earns its place by preventing misrouted queries to the wrong agency.

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?

For a single-parameter read tool with an output schema and full annotation coverage, the description is essentially complete: acquisition path, content scope, and domain boundaries are all present. Only error/empty-result behavior is unaddressed.

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% and the schema already documents the 5-digit pattern, the optional a–d suffix, and where to get the value. The description adds no format or edge-case guidance beyond the schema, 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?

Specific verb + resource + scope: 'Fetch the full record for one CPSC recall by recall number', followed by an enumeration of what the record contains. This is clearly distinguishable from cpsc_search_recalls (search) and cpsc_get_recent (listing), which are named as siblings.

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 routes the agent to cpsc_search_recalls or cpsc_get_recent to obtain the required recall number, and the jurisdiction sentence tells the agent when not to use this tool at all (FDA, NHTSA, USCG, EPA, ATF domains). No explicit statement about behavior when the recall number doesn't exist, so not a 5.

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.