Skip to main content
Glama

China Postal Stats

china_postal_stats
Read-onlyIdempotent

China postal and express-delivery industry statistics from the State Post Bureau (国家邮政局 邮政行业运行情况): postal industry revenue, express revenue (快递业务收入), express volume (快递业务量) and the same-city / inter-city / international split, each as cumulative January-to-month and single-month figures with year-on-year growth exactly as published, plus the release title, date and link. Answers "China express volume Jan-Sep 2026", "快递业务量 9月 同比", "SF Holding industry express revenue YoY", "邮政行业业务收入 累计". Units are 100 million CNY (亿元) and 100 million items (亿件). Give year and month (the release for that month); year alone returns the latest release of that year; no arguments returns the latest release. A month with no release returns found:false plainly with the releases that do exist; nothing is estimated. Source: State Post Bureau of China, postal industry operating statistics.

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": {
      "year": 2026,
      "month": 9
    },
    "name": "china_postal_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year, e.g. 2026. Omit for the latest release.
monthNoMonth 1-12 (the end month of the cumulative window), e.g. 9 for the January-September release. Needs year.

Output Schema

NameRequiredDescriptionDefault
yearNox
foundNo
monthNox
periodNo
sourceNoPublisher and dataset
figuresNonull when the release table could not be read
messageNoExplanation (found:false or figures:null)
releaseNo
data_as_ofNoYYYY-MM
field_notesNo
available_releasesNoReleases that exist (found:false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: a month with no release returns found:false with the list of existing releases, and nothing is estimated. Unit conventions (亿元 / 亿件) and the 'exactly as published' guarantee are also disclosed.

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?

One dense paragraph that front-loads the metric list, then the question archetypes, then invocation and edge-case behavior. The bilingual metric labels and repeated unit notation add bulk, but every clause carries information an agent would otherwise have to guess.

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?

The tool is a two-optional-parameter lookup with an output schema, so return-value documentation is not required, yet the description still covers the one non-obvious return case (found:false) plus units and source. Nothing an agent needs in order to call this correctly is missing.

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%, so the schema already documents both parameters, but the description adds combined-argument semantics the schema does not state: year alone returns the latest release of that year, and month is explicitly the end month of the cumulative window. It effectively compensates for the one dependency the schema only hints at ('Needs year').

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 resource and scope: State Post Bureau postal/express revenue, express volume, and the same-city/inter-city/international split, in both cumulative and single-month form with YoY. The named metrics and source make it unmistakable against the other China data siblings (LPR, house prices, OMO).

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?

Gives concrete query archetypes ('China express volume Jan-Sep 2026', '快递业务量 9月 同比') and spells out the invocation modes: year+month, year alone, and no arguments. It never names an alternative tool or a when-not-to-use condition, which keeps it short of a 5.

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.