Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Newest US consumer product safety recalls (CPSC) in one call: recall number, date, product names, hazards, remedies, man

recalls
Read-onlyIdempotent

Newest US consumer product safety recalls (CPSC) in one call: recall number, date, product names, hazards, remedies, manufacturers, units, link (days=1..30, count up to 50). For marketplaces, retailers and compliance agents. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo1 to 30
countNoup to 50
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new behavior: a per-call price of $0.002 USDC on Base via x402, a payment handshake on first call, and the field set returned. It stops short of disclosing error behavior for unpaid/invalid payment or any rate limits.

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?

Two dense sentences with zero filler: scope and returned fields first, then audience, then pricing. Nothing is repeated and nothing could be cut without losing information.

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?

With no output schema, the description correctly carries the return-field burden and explains the payment flow, which is the main non-obvious behavior. It leaves a gap on defaults for days and count and on payment-failure behavior, which an agent calling a paid endpoint would want to know.

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 every parameter is already described there, including the x_payment first-call semantics. The description only restates the days and count ranges, adding no new meaning such as defaults, timezone for 'date', or how count interacts with days — baseline 3 is appropriate.

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?

Names a specific verb+resource ('Newest US consumer product safety recalls (CPSC)') and enumerates the returned fields (recall number, date, product names, hazards, remedies, manufacturers, units, link), so the agent knows exactly what comes back without opening a schema. No sibling tool overlaps this domain, so no differentiation is required.

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?

Gives audience framing ('For marketplaces, retailers and compliance agents') and the operating ranges (days=1..30, count up to 50), which implies when the tool is appropriate. However, it never states when not to use it, what happens at the boundaries, or how to pick day/count values for a given monitoring cadence — usage is implied rather than prescribed.

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.

Resources