Skip to main content
Glama

Mofcom Series List

mofcom_series_list
Read-onlyIdempotent

Lists the four MOFCOM data-centre series this pack covers (ODI, overseas contracting, labour cooperation, utilised FDI) with their Chinese/English names, units, and the live earliest/latest period each currently has — a cheap discovery call before picking which of the other four tools to use.

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": "mofcom_series_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
foundNo
seriesNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds useful context beyond that: it returns Chinese/English names, units, and the live earliest/latest period for each series, and frames the call as cheap discovery. It does not need to explain returns further because an output schema exists.

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 a single, front-loaded sentence with no wasted wording. It packs purpose, scope, returned metadata, and usage guidance efficiently.

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-parameter discovery tool with annotations and an output schema, the description is complete. It explains what the tool covers, what metadata it exposes, and why an agent should call it before the data-specific siblings.

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?

The tool has zero parameters, so the baseline is 4. The description correctly indicates no filtering or input is needed by describing a simple discovery listing.

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 verb and resource: lists the four MOFCOM data-centre series covered by the pack. It enumerates the series and their metadata, and explicitly positions the tool as discovery rather than data retrieval, making it easy to distinguish from the sibling series tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: a cheap discovery call before picking which of the other four tools to use. This directly names the alternative set and the condition that selects this tool.

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.