Skip to main content
Glama

Recall365 — Global Product Recalls

Get one recall

get_recall
Read-only

Full detail of one recall by its Recall365 id: product, brand, hazard, failed standards, remedy, official notice link.

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": {
      "id": "<id>"
    },
    "name": "get_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecall365 id from search results.
langNoOutput language: zh = 中文, en = English. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 the returned field set (product, brand, hazard, failed standards, remedy, notice link), which is genuinely useful with no output schema, but says nothing about missing-id behavior, error handling, or the effect of the lang parameter.

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?

A single front-loaded sentence with the key qualifier (id-based single-record lookup) stated first and a compact enumeration of returned fields. No filler or redundancy.

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 simple two-parameter read tool with full schema coverage and no output schema, naming the returned fields is the missing piece and it is supplied. Only minor gaps remain, such as not indicating whether the record can be absent or how the language choice affects content.

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 100%, including the enum values for lang and the meaning of id, so the baseline is 3. The description only restates that the id is a Recall365 id and never mentions the language option, adding no meaning beyond the schema.

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?

Names a specific verb ('Full detail') and a specific resource ('one recall') qualified by identifier ('by its Recall365 id'), which contrasts with the list-style siblings like search_recalls. It does not explicitly name the sibling it complements, so it stops short of 5.

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?

'by its Recall365 id' plus the schema note 'Recall365 id from search results' implies the lookup-after-search workflow, so usage is inferable. There is no explicit when-to-use/when-not statement or named alternative such as search_recalls.

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