Skip to main content
Glama
Sign In

China Recalls

by io.github.pipeworx-io
OverviewDiscussionsAdmin

China Get Recall

china_get_recall
Read-onlyIdempotent

One SAMR recall announcement in full: recalling company, units affected, production window, defect and remedy text, issuing unit, publication time and attachments (e.g. the recall plan PDF). Takes the id returned by china_search_recalls. Text is in Chinese.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "2025/art_473b221b409943889be9864d21a2b870"
    },
    "name": "china_get_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAnnouncement id from china_search_recalls, e.g. 2025/art_473b221b409943889be9864d21a2b870.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real behavioral value beyond them: the text is in Chinese and the payload includes attachment artifacts such as the recall plan PDF, which an agent cannot infer from the schema.

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 sentences, each earning its place: content list first, then usage lineage, then language caveat. No filler and front-loaded with the most decision-relevant information.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so by enumerating the fields returned, including attachments. For a single-param fetch-by-id tool this is complete.

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% and the id parameter is fully documented with an example in the schema, so the description need not explain it. It adds no format or syntax detail beyond the schema, warranting the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (SAMR recall announcement) and enumerates exactly what the record contains: company, units, production window, defect/remedy text, issuing unit, publication time, attachments. It is clearly distinguishable from china_search_recalls because it explicitly takes an id rather than query terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly ties usage to the sibling by stating it 'Takes the id returned by china_search_recalls', which establishes the workflow. It lacks an explicit when-not condition, but the context is clear enough for correct selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All China Recalls toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources