Skip to main content
Glama

Recall365 — Global Product Recalls

Search recalls

search_recalls
Read-only

Search official product recalls by keyword (product, brand, hazard; Chinese/English/Korean brand names are cross-matched). Returns at most 20 newest/most relevant notices with links.

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

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: zh = 中文, en = English. Default en.
limitNo
queryNoKeyword, e.g. 'power bank', '婴儿床', 'BMW'. Optional if filters are given.
sinceNoEarliest publish date, YYYY-MM-DD.
offsetNo
countryNoRecall market ISO code, e.g. US, EU, UK, CA, AU, NZ, JP, KR, CN.
categoryNo
made_in_chinaNoOnly products whose origin is China.
border_rejectionNoOnly EU RASFF border rejections (food refused at the EU border, not recalled).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 20-result cap, newest/most-relevant ranking, returned links, and the non-obvious cross-matching of Chinese/English/Korean brand names. It does not mention pagination or the border_rejection caveat, but those gaps are modest.

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?

Two tightly packed sentences with no filler, leading with the core action and following with result shape. The parenthetical is dense but earns its space by describing cross-language matching that an agent could not otherwise predict.

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 9-parameter discovery tool with no output schema, the description covers the query semantics and the return shape, which is the essential part. However, it says nothing about the filter family (country, category, since, made_in_china, border_rejection) or how results are ordered when a keyword is absent, so an agent must read the schema to use the tool well.

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 67% and the schema documents lang, query, since, country and the two booleans in reasonable detail. The description adds semantics only for query (product/brand/hazard terms, multilingual cross-matching) and implicitly for the result cap, leaving since, country, category and offset/filters unexplained beyond the schema — appropriate for the baseline.

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?

Uses a specific verb and resource ("Search official product recalls by keyword") and scopes the searchable fields to product, brand and hazard. It is clearly distinguishable from get_recall in spirit, though it never names a sibling to contrast against.

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 discovery tool for keyword-based recall lookups, while get_recall or brand_recall_history presumably serve ID-level or brand-history cases. No explicit when-to-use or when-not-to-use statement, and no mention that query is optional when filters are supplied (that fact lives only in the schema).

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