Skip to main content
Glama

Mofcom Fdi Utilised

mofcom_fdi_utilised
Read-onlyIdempotent

Utilised inbound foreign direct investment into China (吸收外商直接投资) and newly established FDI enterprises — monthly YEAR-TO-DATE CUMULATIVE figures, each with year-over-year %. Sourced live from MOFCOM's (商务部) data centre, keyless. Values reset down every January. The monetary amount (USD 100M) stopped being published through this feed around mid-2023 — recent rows carry the enterprise COUNT only, with the dollar figure null. Answers "how much FDI is China attracting", "new foreign-invested enterprises in China this year".

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

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

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

Beyond the annotations, it discloses important behavioral traits: live keyless MOFCOM sourcing, year-to-date cumulative values, January resets, and the mid-2023 discontinuation of the USD 100M monetary figure with recent rows carrying null amounts and enterprise counts only. These details materially affect interpretation and are not present in the annotations or 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?

The description is dense but front-loaded: it leads with the core data scope, then adds sourcing, caveats, and example questions. Every sentence contributes useful selection or interpretation context without unnecessary filler.

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 definition is complete for this data-retrieval tool: annotations cover safety and idempotence, the output schema handles return structure, and the description supplies essential data caveats such as YTD cumulative reporting and null monetary values after mid-2023.

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 description coverage is 100%, so start_period, end_period, and limit are already fully documented. The description adds contextual meaning about cumulative YTD periods and January resets, but it does not add parameter-specific syntax or constraints beyond what the schema provides.

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 states a specific resource and scope: utilised inbound FDI into China and newly established FDI enterprises, with monthly year-to-date cumulative figures and YoY percentages. It clearly distinguishes inbound FDI from outbound sibling tools through the term "inbound" and the explicit China focus.

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?

It provides clear usage context by naming the questions it answers, such as "how much FDI is China attracting" and "new foreign-invested enterprises in China this year." It does not explicitly name when not to use it or point to alternatives such as mofcom_odi, but the inbound scope makes the intended context fairly clear.

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.