A股数据 API (A-Share Data API)

ashare_bigorder_flow_full

L2 大单成交·全天完整：把当日全部成交额 ≥ 阈值的大单一次拿全，不受「单次最多 200 笔」限制。用于算全天金额（主力净流入多少、四方向各多少）。行字段与 ashare_bigorder_flow 完全一致；顶层 meta 有 total（当日总笔数）/ returned / deduped（合并掉的重复条数）/ pages / complete（是否已拿全）/ summary（四方向金额合计，summary_scope=all_rows，拿全时即当日全量）。用户问'今天主力净流入多少 / 主动买和主动卖各多少 / 大单金额合计'用这个。⭐ 与 ashare_bigorder_flow 的分工：flow 只给最新 200 笔（快，看方向）；本工具给全天全量（慢，算金额）。只拿 200 笔去算全天金额会算错。⚠️ 比 flow 慢（内部逐页取，每页约 0.8 秒）：30 万档活跃票约 20~30 秒，100 万档约 10 秒，300 万档约 2 秒 ⇒ 只要结论时建议 money=2（100 万）以上。⚠️ 返回量大（5000 行约 600 KB）：只要方向不要金额时，用 ashare_bigorder_flow 更省；确实需要全量但上下文紧张时，可用 max_rows 调小。⚠️ 仅当日。⚠️ 这是成交口径，不是逐笔委托、也不是十档盘口。⚠️ 机构版专属：其他档位返回明确说明 + 升级链接。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "ashare_bigorder_flow_full"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	股票代码：sh600667 或 600667
`money`	No	金额阈值档：0=30万 1=50万 2=100万 3=300万 4=1000万
`max_rows`	No	最多返回多少笔（默认 6000，够装单票全天；调小可省上下文）

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations to lean on, the description carries the full burden and does so: it discloses relative latency (per-page ~0.8s, with 2s/10s/20-30s estimates by money tier), return volume (~600 KB for 5000 rows), day-only scope, the 成交口径 vs 逐笔委托/十档盘口 distinction, and an institutional-tier access restriction with upgrade path. These are exactly the non-obvious traits an agent needs before calling.

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 the core claim and the sibling split, then layered warnings; the emoji markers create scannable structure. It is dense but nearly every sentence adds operational information, with only mild repetition of the 'full-day amount' framing across the opener, the ⭐ block, and the closing example questions.

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 3-parameter tool with an output schema, the description covers everything an agent needs: cost/latency tradeoffs, payload size, scope limits, access gating, and the meaning of the meta fields (total/returned/deduped/pages/complete/summary). Nothing material for correct invocation is missing.

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 baseline is 3; the description still adds value by recommending money=2 (100万) when only a conclusion is needed and by advising max_rows be lowered when context is tight. It does not restate the enum mapping, which the schema already covers.

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: fetch ALL of the day's L2 large-order fills at or above a threshold, explicitly without the 200-row cap. It names the sibling ashare_bigorder_flow and pins down the distinction (flow = latest 200 for direction, this = full day for amount), so an agent can route correctly 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 explicit when-to-use triggers ('今天主力净流入多少 / 主动买和主动卖各多少 / 大单金额合计'), an explicit when-not ('只要方向不要金额时，用 ashare_bigorder_flow'), and a correctness warning that using 200 rows to compute full-day amounts is wrong. Alternatives and exclusions are both spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All A股数据 API (A-Share Data API) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?