Skip to main content
Glama

Mofcom Labor Cooperation

mofcom_labor_cooperation
Read-onlyIdempotent

China's overseas labour dispatch (对外劳务合作) — monthly YEAR-TO-DATE CUMULATIVE count (in 10,000-person units) of Chinese workers dispatched abroad, split by whether they went out under contracted-engineering projects or under standalone labour-cooperation contracts, plus the year-over-year change (an ABSOLUTE change in 10,000-person units, not a percent). Sourced live from MOFCOM's (商务部) data centre, keyless. Values reset down every January. Answers "how many Chinese workers are sent abroad", "China overseas labour export trend".

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": {
      "end_period": "2026-09",
      "start_period": "2026-01"
    },
    "name": "mofcom_labor_cooperation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return, newest first (default 24, max 500). Ignored range still comes from start_period/end_period — this only caps how many of those rows come back.
end_periodNoLatest period to include, as YYYYMM or YYYY-MM. Omit for the most recent available month.
start_periodNoEarliest period to include, as YYYYMM or YYYY-MM (e.g. "2024-01" or "202401"). Omit for full history.

Output Schema

NameRequiredDescriptionDefault
noteNo
rowsNo
foundNo
sourceNo
returnedNo
data_as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses that figures are YEAR-TO-DATE CUMULATIVE (not monthly flow), that values reset every January, that the delta field is an absolute change in 10,000-person units rather than a percent, and that the source is a keyless live MOFCOM feed. These are exactly the traits that cause misreads of a data series, and they are stated up front.

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?

Content is front-loaded with the metric definition before the caveats, and nearly every clause earns its place (units, split, absolute-vs-percent, reset behavior, source). It is dense — a single long paragraph with parenthetical script annotations — which makes it slightly harder to scan than it could be, but nothing is redundant.

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?

An output schema exists, so return shape need not be described, and annotations cover the safety profile. What remains — units, cumulative-vs-flow semantics, reset cadence, delta type, and data provenance — is all supplied, which is complete for a 3-parameter read-only series tool.

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 parameter syntax is already handled and the baseline would be 3. The description earns an extra point because the YTD-cumulative and January-reset semantics materially change how start_period/end_period should be chosen (a range crossing January mixes two accumulation cycles), which the schema does not explain.

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?

The description names a specific metric (monthly year-to-date cumulative count of Chinese workers dispatched abroad, in 10,000-person units), its breakdown (contracted-engineering vs. standalone labour-cooperation), and its companion field (year-over-year ABSOLUTE change). It also disambiguates against the adjacent MOFCOM series by scoping itself to labour dispatch rather than FDI/ODI/contracting.

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?

Usage is implied through the two example questions ('how many Chinese workers are sent abroad', 'China overseas labour export trend') and the 'keyless, live from MOFCOM' note, which tells the agent this is a first-party source. However, there is no explicit when-to-use vs. when-not guidance and no routing to sibling MOFCOM tools such as mofcom_overseas_contracting, even though those overlap conceptually.

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.