Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

valuation_snapshot

Read-onlyIdempotent

获取个股最新估值、市值、换手率、股息率等 daily_basic 指标，适合快速判断估值位置 何时使用: PE/PB/PS/股息率/市值快照；配合 financial_summary。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
codeNo单股查询：股票代码或名称，例如 600519、600519.SH、贵州茅台。
dateNo可选。估值交易日，支持 YYYY-MM-DD 或 YYYYMMDD；不传则取最近可用交易日。
codesNo批量查询：代码或名称数组，例如 ["600519","000001"]。上限 20 只。多股估值横向比较时优先使用 codes。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
embedStockNo是否回完整 stock 档案（行业/地区/交易所等）。不传=false。
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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description need not restate it. It instead adds genuinely new context: the output shape (rows/items/nested stock objects containing code/name) and a mandatory rendering rule that listed stocks be formatted as markdown links. That is useful behavioral guidance beyond the structured fields.

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?

It is a dense, front-loaded block: purpose first, then when-to-use, then the linking rule. Almost every clause earns its place, though the bracketed 【链接】 instruction is slightly instruction-styled and could be tighter.

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, the description need not explain return values, and annotations plus full param coverage carry most of the load. It supplies the key non-obvious behavior (markdown link formatting for tickers), so it is essentially complete, with only minor room for a note on batch size limits beyond what the schema already states.

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 (code, date, codes, format, embedStock, detailLevel) is already documented in the schema, including the 'at least one of code/codes' constraint. The description adds no parameter-level syntax or semantics beyond that, which matches the baseline 3 when the schema does the heavy lifting.

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?

The description names a specific resource (个股) and an explicit metric set — 估值、市值、换手率、股息率 (daily_basic 指标) — and frames the use case (快速判断估值位置). It also signals how it relates to the financial_summary sibling, so an agent can place it precisely among the many market tools.

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 '何时使用' clause explicitly lists the triggering concepts (PE/PB/PS/股息率/市值快照) and names the companion tool financial_summary. It gives clear positive context but no explicit exclusions or 'when not to use' guidance, keeping it short of 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