Skip to main content
Glama

Recall365 — Global Product Recalls

Pre-export risk check

precheck_product
Read-only

Risk profile for a product type before selling it abroad: recalls in the last 3 years, share made in China, top hazards, top markets, yearly trend, typical cases and self-check advice.

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": {
      "product": "<product>"
    },
    "name": "precheck_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: zh = 中文, en = English. Default en.
countryNoRecall market ISO code, e.g. US, EU, UK, CA, AU, NZ, JP, KR, CN.
productYesProduct type, e.g. 'baby stroller', '充电宝'.

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 the safety profile is covered. The description adds useful behavioral scope by naming the exact profile contents, including the 3-year recall window and China manufacturing share, which helps an agent understand what the response will contain.

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?

The definition is a single compact sentence with a colon-delimited list of return contents, and it front-loads the core purpose. The fragment style is slightly less clear than a full sentence, but no wording is wasted.

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 three-parameter, read-only tool with no output schema, the description does a good job listing the return categories so the agent knows what to expect. It does not explain how country affects the profile or clarify the optional language behavior, but those are covered by the schema.

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 input parameters are already well documented. The description does not add syntax, defaults, or parameter-specific meaning beyond what the schema provides, so the baseline of 3 applies.

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 clearly states the resource and scope: a risk profile for a product type before selling abroad, listing the exact data points returned. It is distinguishable from recall-specific siblings like search_recalls or brand_recall_history, though it does not explicitly name those alternatives.

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?

The phrase 'before selling it abroad' implies a pre-export use case, but there is no explicit guidance on when to choose this tool over search_recalls, get_recall, or brand_recall_history. No exclusions or prerequisites are stated, leaving usage selection partly inferred.

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