Skip to main content
Glama

Ashares Capital Flow

ashares_capital_flow
Read-onlyIdempotent

Per-stock daily main-capital net inflow history (主力净流入 / 超大单+大单净流入, often called '超大单净流入' in retail trackers) for a Chinese A-share stock or ETF, one row per trading day with net inflow broken down by order size: 超大单 (super-large/institutional), 大单 (large), 中单 (medium), 小单 (small), plus 主力净流入 (main = 超大单+大单combined) in both CNY amount and as a % of that day's turnover. Answers '主力净流入历史', '超大单净流入', '000768最近20个交易日的主力资金流向', 'main capital net inflow history for a China A-share stock', 'which days did big money flow into/out of a stock'. A positive net inflow means net buying pressure from that order-size bucket that day, negative means net selling. Source: Eastmoney push2his fflow/daykline (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": {
      "code": "000768",
      "days": 20
    },
    "name": "ashares_capital_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes6-digit A-share or ETF code, e.g. "000768" (中航西飞) or "515050". sh/sz/bj prefixes accepted but optional.
daysNoHow many of the most recent trading days to return, 1-200 (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"How many of the most recent trading days to return, 1–200 (default 20)."New value: +"How many of the most recent trading days to return, 1-200 (default 20)."
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine context beyond that: the upstream source (Eastmoney push2his fflow/daykline, keyless) and the sign convention (positive = net buying pressure, negative = net selling). It says nothing about rate limits, empty results for non-trading days, or pagination/volume limits at days=200.

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?

Purpose is front-loaded in the first clause, and the sentence structure moves from what it is to the breakdown to example queries to sign semantics. It is somewhat dense and carries mild redundancy in the alias stack ('主力净流入 / 超大单+大单净流入, often called 超大单净流入'), but nearly 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?

There is no output schema, so the description must carry the return shape — and it does, describing one row per trading day with 超大单/大单/中单/小单 and combined 主力净流入 in both CNY and % of turnover. For a 2-parameter read tool with full annotation coverage this is close to complete; only edge-case behavior (ETFs vs stocks, non-trading days, truncated history) is unaddressed.

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 description coverage is 100%, with `code` documented as a 6-digit A-share/ETF code with accepted prefixes and `days` documented as 1-200 with default 20. The description adds no parameter-level meaning beyond this; its detail is about output columns rather than inputs, 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+resource+scope: per-stock daily main-capital net inflow history for a Chinese A-share stock or ETF, with the row granularity (one row per trading day) and column breakdown spelled out. 'Per-stock' implicitly and effectively distinguishes it from the sibling aShares_sector_capital_flow, so an agent can route without opening the 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?

Provides concrete trigger phrases ('主力净流入历史', '000768最近20个交易日的主力资金流向', 'which days did big money flow into/out of a stock'), which gives a clear sense of when to use it. It stops short of explicitly naming alternatives or stating when not to use it (e.g., sector-level vs stock-level), so it does not reach 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.