Skip to main content
Glama

Recall365 — Global Product Recalls

Brand recall history

brand_recall_history
Read-only

Recall history of a brand across all markets: totals by year, country and category, plus the 10 latest notices.

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": {
      "brand": "<brand>"
    },
    "name": "brand_recall_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: zh = 中文, en = English. Default en.
brandYesBrand name, e.g. 'Anker', '小米'.

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral value beyond that by disclosing the shape of the result (totals by year, country and category) and a concrete cap ('the 10 latest notices'), which matters because there is no output schema. It does not say whether that 10-item limit is configurable or how large result sets are handled.

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?

A single front-loaded sentence with a colon-delimited list of what is returned; no filler. 'Across all markets' is slightly redundant with the country breakdown that follows, but the sentence earns its place overall.

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?

For a two-parameter read-only lookup with no output schema, the description covers purpose, scope and the composition of the response, which is what an agent needs to call it correctly. The remaining gap is routing guidance relative to the sibling recall tools.

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%, with both 'brand' and the 'lang' enum documented in the schema itself, so the baseline is 3. The description adds nothing about parameter behavior, such as whether brand matching is exact or fuzzy, or how lang affects the returned notice text.

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 resource and scope: 'Recall history of a brand across all markets', and enumerates the aggregation dimensions (year, country, category) plus the latest notices. It is clearly a historical/aggregate lookup rather than a single-record fetch, which implicitly separates it from get_recall and search_recalls, though it never names those siblings.

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 aggregate brand-level recall history, but there is no explicit 'use this when...' statement, no exclusions, and no mention of when to prefer get_recall or search_recalls instead.

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