Wudao A-Share Stock Data MCP

convertible_bond_market

Read-onlyIdempotent

查询可转债搜索、正股映射、实时快照、涨幅/成交额排行、日线、分钟线和转股溢价率。可转债是独立资产，不要当作股票涨停或股票筛选工具使用。何时使用: 可转债行情工具：查转债搜索、正股映射、实时快照、涨幅/成交额排行、日线、分钟线和转股溢价率。不要把可转债当股票涨停工具使用。

Input Schema

Name	Required	Description	Default
`code`	No	可选。单个可转债代码；等价于 symbols 单元素。
`mode`	No	查询模式，默认 snapshot。search=搜索可转债；snapshot=实时快照；rank=排行；daily=日线；minute=分钟线。	snapshot
`limit`	No	返回数量，snapshot 默认 30，rank 默认 50；日线/分钟默认返回尾部窗口。
`order`	No	排序方向，默认 desc。	desc
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`period`	No	minute 模式周期，默认 1m。	1m
`sortBy`	No	rank/snapshot 排序字段，默认 pctChg；可选 pctChg/amount/close/vol/conversionPremiumRate/premiumRate。	pctChg
`endDate`	No	可选。daily 模式结束日期，支持 YYYY-MM-DD 或 YYYYMMDD。
`keyword`	No	可选。名称/代码/分类关键词。search 模式按关键词搜索；snapshot/rank 模式用于过滤。
`symbols`	No	可选。可转债代码，数组或逗号分隔字符串。daily/minute 模式建议显式传入。
`startDate`	No	可选。daily 模式起始日期，支持 YYYY-MM-DD 或 YYYYMMDD。
`tradeDate`	No	可选。交易日期，支持 YYYY-MM-DD 或 YYYYMMDD；daily/minute 模式可指定日期。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
`forceRefresh`	No	调试用。true 时绕过共享结果缓存；指数实时模式仍只读取最新落盘快照，不会由用户请求触发现场刷新。

Output Schema

Name	Required	Description	Default
`data`	No
`meta`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

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。"

Changed1 schema field changedOct 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {},
+    "meta": {},
+    "success": {}
+  },
+  "type": "object"
+}

First observedOct 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the asset-class caveat and mode list, with nothing on caching, rate limits, or the cache-bypass nuance that the schema mentions. Useful but thin beyond the annotations.

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 capability list and the '何时使用' section repeat the same enumeration ('转债搜索、正股映射、实时快照、涨幅/成交额排行、日线、分钟线和转股溢价率' appears twice), wasting space. The asset-class warning is valuable, but the duplication means not every sentence earns its place.

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?

Covers the tool's scope and asset-class boundaries, and with an output schema present it needn't explain return values. For a 14-parameter multi-mode tool with annotations covering safety, it is nearly complete, though it could clarify how modes interact with the optional filters.

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% and 14 parameters are each documented, including mode enum behavior, defaults and sortBy fields. The description adds no syntax or format detail beyond the schema, 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 resource (可转债) with concrete capabilities: search, underlying-stock mapping, realtime snapshot, gain/turnover ranking, daily and minute bars, conversion premium rate. It explicitly distinguishes itself from siblings by warning '可转债是独立资产，不要当作股票涨停或股票筛选工具使用', clearly separating it from limit_up and stock_screener.

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 (可转债行情工具) and a clear when-not ('不要把可转债当股票涨停工具使用'), routing the agent away from the stock limit-up/screening tools. The misuse exclusion is stated up front rather than left to inference.

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 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.