Skip to main content
Glama

BRAINIAC Product Safety & Recalls

Search CPSC product recalls

product-safety_cpsc-recall-search
Read-onlyIdempotent

Search US CPSC recalls by keyword, firm, recall number, UPC or date range in the vendored snapshot. Price $0.03 USDC. POST /api/v1/product-safety/cpsc-recall-search. An unpaid call returns the x402 payment terms and does not run.

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": "product-safety_cpsc-recall-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoto, string. Optional.
upcNoupc, string, length 6 to 14. Optional.
firmNofirm, string, length 1 to 120. Optional.
fromNofrom, string. Optional.
limitNolimit, integer, from 1 to 100. Required.
queryNoquery, string, length 2 to 120. Optional.
recallNumberNorecallNumber, string, length 1 to 40. Optional.

Output Schema

NameRequiredDescriptionDefault
countNocount. Number.
recallsNorecalls. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
snapshotDateNosnapshotDate. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses the two things an agent most needs: a cost of $0.03 USDC and the x402 payment flow, including the exact failure mode that an unpaid call returns payment terms and does not execute. It also discloses that results come from a vendored snapshot rather than live data.

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?

Three short sentences, front-loaded with the capability before pricing and transport details; nothing is padded. The explicit endpoint path partly duplicates what the tool name already conveys, which is the only inefficiency.

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?

An output schema exists, so return-value documentation is unnecessary, and the description still covers cost, payment behavior, data provenance, and filter surface for a 7-parameter tool. The only minor omission is snapshot freshness or recency, which does not block correct invocation.

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%, so the baseline is 3. The description adds modest value by grouping the filters semantically (keyword, firm, recall number, UPC, date range), but it does not mention 'limit' or clarify whether the filters combine as AND or OR, so the schema still carries the real burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Search US CPSC recalls') plus the exact match dimensions (keyword, firm, recall number, UPC, date range) and the data source ('vendored snapshot'). The 'US CPSC' qualifier implicitly separates it from the Canada/EU/FSA siblings, but no sibling is named or contrasted explicitly.

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?

Usage is only implied: an agent can infer this is the tool for US CPSC recall lookups from the jurisdiction and filter list. There is no explicit when-to-use/when-not-to-use guidance, no statement about when a sibling jurisdiction tool is the better choice, and no note on what to do if no filters are supplied.

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