Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

stock_research_workflow

Read-onlyIdempotent

一键生成个股研究数据包：股票搜索、K 线、个股资金流、研报、龙虎榜，并可附带估值、财务摘要和股东结构。 何时使用: 一键个股研究：K 线/资金流/研报/龙虎榜，可选估值/财务/股东。默认 digest。短线场景可关 includeFundamental。

Input Schema

NameRequiredDescriptionDefault
codeYes必填。股票代码或名称，例如 600519、600519.SH、贵州茅台。
daysNoK 线天数，默认 30。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
returnModeNodigest=仅 stepDigest 摘要+nextActions（默认）；structured=各子步骤完整 data；rawSteps=完整 step 调试。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
includeFundamentalNoAgent 自动判断。是否包含估值、财务摘要和股东结构，默认 true。中长线/基本面研究保持 true；短线盘口、涨停、龙虎榜或资金流问题可设为 false。

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/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds the default digest output mode and the short-term-liquid exclusion, which is useful, but says nothing about rate limits, latency of a multi-domain aggregation, or failure behavior when a sub-source is unavailable.

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

Conciseness5/5

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

Two tightly packed lines: what it produces first, then when to use it and the one toggle that matters. No filler, front-loaded, and the domain list doubles as routing 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?

For a six-parameter composite tool with an output schema present, the description covers the aggregation scope, the default mode, and the fundamental toggle. It stops short of explaining how the optional sections are merged into output or how digest vs structured changes what the agent receives, which is the main remaining gap.

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 every parameter including enum-like options (format, returnMode, detailLevel) is already documented in the schema. The description reinforces includeFundamental's tradeoff but adds no syntax or format detail beyond what the schema provides; 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 composite action (一键生成个股研究数据包) and enumerates the bundled data domains (K线、资金流、研报、龙虎榜、估值、财务、股东结构). An agent can immediately distinguish this aggregator from the single-purpose siblings like kline, dragon_tiger, or valuation_snapshot.

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 a clear 何时使用 line naming the one-click research scenario, and adds a concrete exclusion: 短线场景可关 includeFundamental. It does not explicitly state when to bypass this tool in favor of individual sibling calls (e.g., for a single K-line lookup), which keeps it below a 5.

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