SiteCheck Shop & Social

U.S. Consumer Product Safety Commission product recalls

ecommerce_cpsc_recalls

Read-only

U.S. Consumer Product Safety Commission product recalls from SaferProducts.gov. Searches recall titles only (not all text). Returns recall number, date, hazard, remedy and the official CPSC page. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "ecommerce_cpsc_recalls"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Words that must appear in the recall title, 2 to 100 characters
`limit`	No	How many recalls to return, 1 to 20 (default 5)

Output Schema

Name	Required	Description	Default
`q`	No
`total`	No
`source`	No
`recalls`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely non-obvious behavior: a per-call price of $0.002 USDC charged only on success via x402 across Base, Solana or Arc, plus which fields come back. That is meaningful context beyond structured data, though it omits rate limits and how broad the title matching is.

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?

The capability and its scoping limit are front-loaded in the first sentence, followed by return contents and pricing. The pricing sentence is long but earns its place by warning the agent about per-call cost; nothing is filler.

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?

An output schema exists, so return values need not be enumerated, yet the description lists them helpfully. With two fully documented parameters, safety annotations and pricing disclosed, the definition is close to complete; only pagination or result-ordering behavior is left unstated.

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%, with both q and limit already documented including the 2-100 character range and 1-20 limit with default 5. The description's 'titles only' phrase restates what the q schema already says, so it adds little meaning beyond the structured fields; 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: searches U.S. CPSC product recalls from SaferProducts.gov, plus the crucial scope constraint that it matches titles only. The source and jurisdiction ('U.S. Consumer Product Safety Commission') implicitly separate it from the EU RAPEX sibling, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'titles only (not all text)' note tells the agent it cannot do full-text recall searches, which is a real usage constraint. However, no explicit when-to-use or when-not guidance is given and no alternative tool is named, so the agent must infer applicability from the name alone.

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

All SiteCheck Shop & Social 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?