Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

northbound_holdings

Read-onlyIdempotent

查询沪深股通持股明细。传 code 返回个股北向持股历史，不传 code 可按日期查看全市场明细；marketType 可选 SH/SZ。 何时使用: 北向持股：沪深股通个股持股和全市场持股明细。用于判断外资持仓变化，注意数据通常下个交易日更新。

Input Schema

NameRequiredDescriptionDefault
codeNo可选。股票代码或名称；传入则返回个股沪深股通持股历史，不传可按日期查全市场明细。
limitNo返回数量，默认 100，最大 500。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
endDateNo区间结束日期。
startDateNo区间开始日期。
tradeDateNo单日交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。与 startDate/endDate 二选一。
marketTypeNo可选。沪深股通市场过滤，常用 SH/SZ；不传不限。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / detailLevel / description
      Previous value: -"输出详细度（不传=standard，返回 Agent 可计算标准字段）。summary=压缩摘要；raw=全字段+原始数据。"New value: +"档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。"
    • changedInput schema / properties / format / description
      Previous value: -"content[0].text 形态。通常不传=1 行 headline；auction_market_scan / auction_theme_strength 在 standard/raw 档默认直接返回 JSON 明细。markdown=完整 markdown 表格；json=完整 JSON。"New value: +"content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {},
+    "meta": {},
+    "success": {}
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds one genuine behavioral fact beyond annotations: the next-trading-day data update lag, which matters for interpreting results. It offers nothing further (no rate limits, coverage windows, or freshness for historical ranges).

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 and the two sentences are compact. There is mild redundancy across the two paragraphs (沪深股通持股明细 is restated, and the code behavior appears in both the first sentence and the schema), which slightly dilutes efficiency but does not obscure anything.

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 no explanation, and all 8 params are documented. The description covers the dual query modes, market filter, and data-update timing, leaving only minor gaps (e.g., which sibling to prefer for related foreign-flow questions).

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%, so the schema already documents every parameter including code, marketType (SH/SZ), tradeDate vs startDate/endDate exclusivity, and detailLevel. The description largely restates code and marketType semantics rather than adding new meaning, 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 (查询) and resource (沪深股通持股明细) and explains the dual-mode behavior: passing code returns per-stock northbound history, omitting it returns whole-market detail by date. An agent can immediately tell this is the northbound/Stock-Connect holdings tool, distinct from generic capital_flow or shareholder_structure siblings.

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?

The '何时使用' block gives clear context (northbound holdings; judge foreign capital position changes) and a useful freshness caveat ('数据通常下个交易日更新'). It does not, however, name explicit alternatives or when-not-to-use conditions among the many siblings.

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

All Wudao A-Share Stock Data MCP toolsInspect
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