Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

sector_analysis

Read-onlyIdempotent

板块轮动四象限分析（动量 × 强度），默认开盘啦题材口径；也可切行业/财联社概念 何时使用: 板块轮动四象限，默认开盘啦题材口径（source=kpl）；行业用 source=industry；财联社概念兼容 source=cls_concept。配合 theme_intraday_capital / theme_stocks。

Input Schema

NameRequiredDescriptionDefault
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
periodNo分析周期，默认 60。
sourceNo板块分类口径，默认 kpl=开盘啦题材；可传 kpl/kaipanla、industry（财联社行业）、cls_concept（财联社概念兼容）、theme（站内旧题材）。concept 别名也映射到 kpl。kpl
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
strengthPeriodNo强度周期，默认 5。

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

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

Annotations already cover readOnly, idempotent, non-destructive, openWorld. The description adds source/period semantics but doesn't go beyond what is implied. It does note default口径 (kpl) and compatibility mapping (concept→kpl), which is useful behavioral context not in annotations. Still, safety profile is fully covered by annotations, so modest added value.

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?

It includes a 何时使用 section which is good structure, but the text is repetitive (source mapping appears in both description and schema), and the bilingual style is dense. Front-loads the core purpose, but verbosity reduces efficiency.

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?

Has an output schema, so return values needn't be explained. For an analysis tool with 5 optional params, the description covers purpose, when-to-use, source alternatives, and companion tools. Slight gap: no mention of what the four quadrants mean or output structure, but given output schema exists, this is reasonably complete.

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 coverage is 100%, so the schema already documents all parameters. The description echoes some source/period info but largely duplicates the schema enum descriptions (e.g., source mapping concept→kpl). Baseline 3 is appropriate since the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific analysis: 板块轮动四象限分析 (momentum × strength quadrant analysis), which is a concrete analytical method. Sibling tools like theme_intraday_capital and theme_stocks are about capital/stocks, so this quadrant framing distinguishes it reasonably well. However, the description is dense and bilingual switching reduces immediate clarity.

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?

Explicitly states when to use: for 板块轮动四象限, with source selection guidance (default kpl/开盘啦题材, industry for 行业, cls_concept for 财联社概念). Names companion tools theme_intraday_capital / theme_stocks. This is clear when-to-use plus source routing.

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