Skip to main content
Glama

China Trade Summary

china_trade_summary
Read-onlyIdempotent

China's total monthly merchandise trade, exports, imports, balance, in both USD and CNY (unit: 100 million), with official month-on-month and year-on-year percent changes, exactly as published by the General Administration of Customs (GACC) on its English site's 'preliminary' flash release. Defaults to the latest published month; pass month ("YYYY-MM") for an earlier one within the currently-linked range (see available_months in the response). Published on roughly a 1-week-after-month-end lag; a revised 'final' figure follows in GACC's next monthly cycle. 中国海关总署(GACC)月度进出口总值(美元、人民币),含环比、同比百分比。

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

Input Schema

NameRequiredDescriptionDefault
monthNoMonth as "YYYY-MM", e.g. "2026-07". Omit for the latest published month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so safety is covered. The description adds genuinely new behavioral context: a ~1-week-after-month-end publication lag, the fact that these are 'preliminary' flash figures later superseded by a revised 'final' in GACC's next cycle, and a pointer to `available_months` in the response for the valid range. It doesn't state failure behavior for out-of-range months, which keeps it from a 5.

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 English portion is densely front-loaded: it says what is returned, where the valid months come from, then caveats the latency and revision status. The trailing Chinese sentence largely restates the dataset scope in another language, which is mild redundancy rather than harmful clarification.

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 burden and does it: it enumerates returned fields, units (100 million), both currencies, the MoM/YoY percentages, and points to `available_months` in the payload. Revision status and publication lag round out what an agent needs to interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single `month` parameter is already fully documented with format and example, so the baseline would be 3. The description goes beyond it by specifying the effective valid range ('within the currently-linked range') and telling the agent where to discover that range (`available_months` in the response), which is meaning the schema cannot express.

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 the specific dataset (total monthly merchandise trade: exports, imports, balance), the currencies and units, and the source (GACC preliminary flash release). Calling it 'total' merchandise trade implicitly separates it from the by-commodity and by-country siblings, though it never names those alternatives explicitly.

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?

It gives clear default behavior ('Defaults to the latest published month') and when to pass `month` for an earlier period, which is useful operational guidance. It stops short of saying when to prefer this tool over china_trade_by_commodity, china_trade_by_country, or china_trade_indices, so routing is left to inference from the names.

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.