Skip to main content
Glama

Cn Futures Products

cn_futures_products
Read-onlyIdempotent

List every product in one China futures exchange's daily report (SHFE, INE, ZCE or GFEX) for a trading day, ranked by open interest: contract count, total volume, total open interest, main contract and its settlement, and whether the product has any trading activity. Use to discover product codes before cn_futures_daily. Defaults to the latest published trading day.

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": {
      "date": "2026-11-06",
      "exchange": "ZCE"
    },
    "name": "cn_futures_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoTrading day, YYYY-MM-DD or YYYYMMDD. Omit for the latest published day.
exchangeYesExchange to list

Output Schema

NameRequiredDescriptionDefault
sourceNo
exchangeNo
productsNo
data_as_ofNo
trade_dateNo
exchange_nameNo
product_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior: the default to the latest published trading day, the open-interest ranking, and the inclusion of an activity flag. It does not discuss pagination or failure modes for unpublished days, keeping it short of a 5.

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?

One dense sentence enumerating scope and returned fields, followed by a short routing sentence. Front-loaded with the verb and resource, and no sentence 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 values need not be explained, yet the description still summarizes the key fields. For a two-parameter read-only listing tool, nothing an agent needs to invoke 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% and both parameters are documented in the schema, including the enum and the date format. The description restates the exchange set and the latest-day default but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ('List every product in one China futures exchange's daily report'), names the four valid exchanges, and specifies the ranking (open interest) and returned fields. It explicitly distinguishes itself from cn_futures_daily, so an agent can tell the two apart without opening either schema.

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?

Gives an explicit use case ('Use to discover product codes before cn_futures_daily'), which both names the alternative and states the sequencing condition that selects this tool. The only minor gap is the absence of an explicit when-not-to-use clause.

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.