Skip to main content
Glama

China Exchange Data

Ashares Sector Flows

ashares_sector_flows
Read-onlyIdempotent

深交所 A股行业板块统计, SZSE-official per-industry (行业) turnover ranking for the Chinese A-share market: turnover amount (成交金额/亿元), share volume, company count, total and float market cap, and weighted-average P/E, one row per SZSE industry classification (A 农林牧渔 ... T 综合 etc.), for a given trading day. This is the exchange's own published turnover-by-industry statistic, NOT the vendor-computed "主力资金净流入" (large-order net capital inflow) metric that East Money / 同花顺-style trackers publish; neither SZSE nor SSE discloses that classification publicly, so it is not offered here. Answers "今天A股行业板块成交额排名", "which sectors traded the most today", "SZSE industry turnover ranking". Sorted by turnover amount descending. Source: SZSE ShowReport CATALOGID=1804_gptj_merge_after (keyless).

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": {
      "top": 10
    },
    "name": "ashares_sector_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many industries to return, 1-50 (default 10, all if omitted total is under that).
dateNoTrading day as YYYY-MM-DD (default: today). SZSE returns the most recently published session if the exact date has no data yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world, so the description doesn't need to restate safety. It does add real behavioral facts: the source is the SZSE ShowReport catalog endpoint, it is keyless, results are ordered by turnover descending, and coverage is SZSE industries only rather than all A-shares.

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-loads the resource and scope, then the disambiguation, then the example queries. It is fairly long and mixes Chinese and English labels with some repetition (e.g. naming both exchanges while returning SZSE data), but each major clause carries information an agent would otherwise have to guess.

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 no output schema, the description compensates by enumerating the returned fields (成交金额 in 亿元, share volume, company count, total/float market cap, weighted-average P/E). Combined with the descending sort and the SZSE-only industry coverage, an agent has enough to interpret results, though it does not describe how classification codes (A–T) are formatted.

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 both parameters are already fully documented in the schema. The description only reinforces that the data is scoped to 'a given trading day', matching the date parameter, without adding format or range detail beyond the schema. 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?

Names a specific verb+resource+scope: SZSE-official per-industry turnover ranking for the Chinese A-share market, one row per 行业 classification, sorted by turnover descending. It explicitly separates itself from the vendor '主力资金净流入' metric that similarly named trackers publish, so an agent can tell what data it will and won't get.

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 concrete question shapes it answers ('今天A股行业板块成交额排名', 'which sectors traded the most today'), which is a clear when-to-use signal, and an explicit when-not (large-order net capital inflow is not available here). It stops short of naming a sibling tool to use instead for that need, which would have made it a 5.

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.