Skip to main content
Glama

Mofcom Overseas Contracting

mofcom_overseas_contracting
Read-onlyIdempotent

China's overseas contracted engineering projects (对外承包工程) — monthly YEAR-TO-DATE CUMULATIVE value of newly signed contracts and completed turnover, both in USD 100M, each with year-over-year %. Sourced live from MOFCOM's (商务部) data centre, keyless. Values reset down every January. Answers "value of China's overseas construction/engineering contracts", "Chinese contractors' overseas project turnover".

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_overseas_contracting"
  }
}

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.2/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, open-world read, so the description's job is to add interpretation context — and it does: values are YEAR-TO-DATE CUMULATIVE (not monthly flows) and reset downward every January, which prevents a serious misreading of the series. It also discloses the live keyless MOFCOM source and the USD 100M unit. It doesn't mention reporting lag or how fresh the newest month is.

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?

Front-loaded with the resource, then units, source, and the critical January-reset caveat, then the question phrasings. Dense but nearly every clause earns its place; the parenthetical Chinese terms and source attribution add modest bulk.

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?

For a zero-required-parameter read tool with a full input schema, an output schema, and complete annotations, the description covers the remaining interpretive risks — cumulative-vs-flow semantics, annual reset, units, and provenance. Nothing an agent needs in order to call or interpret it correctly is missing.

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%, so start_period, end_period, and limit are already fully documented, including format and defaults. The description adds only the general framing that rows are monthly and cumulative, which indirectly informs period selection but gives no extra detail on the parameters themselves. Baseline 3 applies.

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?

Names a specific and unusual resource — China's overseas contracted engineering projects — and pins down exactly what is measured: monthly year-to-date cumulative newly signed contracts and completed turnover in USD 100M with YoY%. The 对外承包工程 gloss plus the two example questions leave no ambiguity about which MOFCOM dataset this is versus mofcom_fdi_utilised or mofcom_odi.

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?

The quoted user questions ('value of China's overseas construction/engineering contracts', 'Chinese contractors' overseas project turnover') give concrete trigger conditions for selecting this tool. It does not explicitly exclude adjacent datasets or name a sibling to use instead, so it stops short of full when/when-not guidance.

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.