Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

margin_trading

Read-onlyIdempotent

查询融资融券市场汇总或个股明细。传 code 返回 margin_detail，不传 code 返回交易所汇总 margin；支持 tradeDate 或 startDate/endDate。 何时使用: 融资融券：不传 code 返回交易所汇总，传 code 返回个股融资融券明细。用于判断杠杆资金拥挤、融资余额变化和券源/融券压力。

Input Schema

NameRequiredDescriptionDefault
codeNo可选。股票代码或名称；传入则返回个股融资融券明细，不传则返回交易所汇总。
limitNo返回数量，默认 60，最大 200。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
endDateNo区间结束日期。
startDateNo区间开始日期。
tradeDateNo单日交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。与 startDate/endDate 二选一。
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the response shape is polymorphic (summary vs. per-stock detail) depending on whether code is supplied. It does not discuss pagination or date-range limits, so it is not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core branching logic is front-loaded, but it is stated twice in near-identical form ('传 code 返回 margin_detail，不传 code 返回交易所汇总' then again in the 何时使用 clause), which is avoidable repetition for a tool whose schema already documents the same rule.

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?

An output schema exists, so return values need not be explained; annotations cover the safety profile; and the description supplies the usage context and mode-selection rule. Nothing an agent needs to invoke this correctly is missing.

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 all seven parameters are already documented in the schema, including the code branch and the tradeDate vs. startDate/endDate exclusivity. The description restates the code branch without adding syntax or format detail beyond the schema, so the baseline of 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?

States a specific verb and resource (query margin trading market summary / individual-stock details) and encodes the polymorphic contract: code present returns margin_detail, absent returns exchange-level margin. This distinguishes it clearly from siblings like capital_flow or dragon_tiger, which cover different capital dimensions.

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?

An explicit '何时使用' section states the usage context (leverage-capital crowding, margin balance shifts, securities-lending pressure) and the code-vs-no-code branch that selects the mode. It stops short of naming an alternative tool or a when-not-to-use case, so it is clear context without exclusions.

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