Skip to main content
Glama

Cn Futures Daily

cn_futures_daily
Read-onlyIdempotent

Daily settlement report for one China commodity futures product on one trading day: every contract's open, high, low, close, settlement, prior settlement, volume (lots), open interest and turnover, plus a main contract (highest open interest). Covers SHFE (rebar rb, gold au, silver ag, copper cu...), INE (crude sc, rubber nr...), ZCE (cotton CF, sugar SR, apples AP...) and GFEX (lithium carbonate lc, industrial silicon si...). A listed-but-dormant product (e.g. ZCE wheat WH) returns status "no_listed_activity" with an explanation, not an empty list. DCE (Dalian) is not available. Prices in CNY. 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",
      "product": "rb",
      "exchange": "SHFE"
    },
    "name": "cn_futures_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoTrading day, YYYY-MM-DD or YYYYMMDD. Omit for the latest published day. Weekends and holidays have no file.
productYesExchange product code, case-insensitive: "rb" rebar, "au" gold, "ag" silver, "CF" cotton, "WH" wheat, "lc" lithium carbonate
exchangeNoOptional. Inferred from the product code when omitted.

Output Schema

NameRequiredDescriptionDefault
unitsNo
sourceNo
statusNo
productNo
currencyNo
exchangeNo
contractsNo
data_as_ofNo
trade_dateNo
product_nameNo
exchange_nameNo
main_contractNo
contract_countNo

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, so the description's job is added context — and it delivers: dormant listed products return status "no_listed_activity" with an explanation rather than an empty list, weekends/holidays have no file, prices are in CNY, and a main contract is designated by highest open interest. These are exactly the non-obvious behaviors that prevent an agent from misreading an empty or unusual response.

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 purpose and scope, and the edge-case notes (dormant product, DCE exclusion, defaults) are tight one-liners with no filler. The per-field enumeration is somewhat redundant given an output schema exists, which keeps it just under the top mark.

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 read-only lookup with three parameters, full schema coverage, and an output schema, the description covers everything an agent needs: coverage universe, default date behavior, exchange inference, and the edge cases that would otherwise be misread. Nothing material is left to inference.

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 date format, case-insensitive product code, and the exchange enum with inference are already fully documented in the schema. The description restates the default-to-latest behavior and repeats the exchange list rather than adding syntax or constraint detail beyond it. Baseline 3 is appropriate.

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 ('daily settlement report for one China commodity futures product on one trading day') and enumerates the exact fields returned plus the main-contract rule (highest open interest). The scope boundaries are explicit: exchanges covered (SHFE/INE/ZCE/GFEX) and one explicitly excluded (DCE). An agent can distinguish this from cn_futures_products or cn_futures_warehouse_stocks without opening any schema.

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?

Gives clear operating context: omit the date for the latest published trading day, exchange is inferred from product code, and DCE data is unavailable so the agent should not attempt it. It stops short of explicitly naming a sibling for product discovery or stating a when-not-to-use condition, so it is strong but not a full when/when-not/alternative routing block.

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.