Skip to main content
Glama

find_recall_candidates

Read-only

Return source-linked CPSC notice candidates for GTIN, model or product name. No-match results do not establish safety or absence of a recall. Free research pilot.

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": "find_recall_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
gtinNoValid GTIN-8, UPC-A, EAN-13 or GTIN-14, including check digit. Keep leading zeroes.
modelNo
product_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds two things not in structured data: that results are source-linked candidates (not confirmed recalls) and that an empty result is not evidence of safety. The 'free research pilot' note also flags cost/availability status. It stops short of disclosing result caps, pagination, or ranking behavior.

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?

Three short sentences with zero padding, front-loaded with the core action and followed by the two caveats that most change agent behavior. Every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read-only lookup with no output schema, the description covers what kind of objects come back and how to interpret empties, but leaves result volume, combination semantics, and the relationship to the coverage sibling 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 coverage is only 33%, so the description must compensate more than it does; it names all three accepted keys, which aids recognition, but never says whether they can be combined, which takes precedence, or how multiple matches are treated. The GTIN format detail lives in the schema, not the description.

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 uses a specific verb and resource ('Return source-linked CPSC notice candidates') and names the three lookup keys (GTIN, model, product name), so an agent knows exactly what the tool fetches. It does not, however, contrast itself with the sibling get_recall_coverage, leaving the boundary between the two tools implicit.

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: the identifier-based framing signals that this is the lookup path for a specific product, and the no-match caveat tells the agent how to read a negative result. There is no explicit when-to-use/when-not statement and no routing to the alternative coverage tool, so the agent must infer selection.

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