Skip to main content
Glama

Cn Futures Warehouse Stocks

cn_futures_warehouse_stocks
Read-onlyIdempotent

Shanghai Futures Exchange daily warehouse-receipt (warrant) stocks: gold and silver in kilograms, base metals, rebar, hot-rolled coil and other products in tonnes, with the day-over-day change and the per-warehouse breakdown. This is stock made into warrants for delivery, not total physical inventory. Pass a product code or name (au, ag, rb, copper...) for the full breakdown, or omit it for a one-line total per product. Defaults to the latest published report.

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": "ag"
    },
    "name": "cn_futures_warehouse_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoReport day, YYYY-MM-DD or YYYYMMDD. Omit for the latest published report.
productNoProduct code or name: "au" or "gold", "ag" or "silver", "rb", "cu"... Omit for every product's total.

Output Schema

NameRequiredDescriptionDefault
basisNo
sourceNo
name_enNo
productNo
exchangeNo
sectionsNo
data_as_ofNo
report_dateNo
exchange_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description focuses on domain semantics and does so well: it clarifies the data is warrant/delivery stock rather than total physical inventory, gives units per product family, and states that the latest published report is the default. It does not discuss publication timing, holidays, or limits on historical depth, which are the remaining behavioral unknowns.

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?

Three tight sentences, front-loaded with what the dataset is before describing call options. The only redundancy is the closing 'defaults to the latest published report,' which restates the date parameter description. Almost every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and the description is complete on the dimensions an agent needs: what the metric means, units, granularity, and the default-date behavior. Minor gaps remain around data availability window and report publication cadence, but nothing that would cause a mis-call.

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?

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds meaning the schema does not spell out, namely the shape difference between passing a product (full per-warehouse breakdown) and omitting it (one-line total per product). The unit distinctions (kilograms for gold/silver, tonnes for base metals and steel) further clarify what the returned figures mean. It does not add accepted-name variants beyond the examples already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: SHFE daily warehouse-receipt (warrant) stocks, with units per product group and the day-over-day/per-warehouse detail included. It also disambiguates the concept itself ('this is stock made into warrants for delivery, not total physical inventory'), which is a real source of confusion. It stops short of naming when to prefer it over siblings like cn_futures_daily or cn_futures_products.

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

Usage Guidelines3/5

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

Usage guidance is limited to how to shape the call ('pass a product code or name for the full breakdown, or omit it for a one-line total per product'), which is parameter behavior rather than tool selection. There is no statement of when to use this versus the related futures tools, nor of any prerequisites. Adequate but leaves the routing decision to inference.

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.