Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

anomaly_detection

Read-onlyIdempotent

按交易所规则检测个股价格偏离基准指数的异动：3日偏离±20%/±30%（主板/双创），主板风险警示股历史按生效日切换旧/新口径，10日严重异动等，自动区分板块阈值 何时使用: 监管口径异动和风险提示；主板风险警示股票按规则生效日自动切换旧/新异常波动口径。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
codeNo股票代码或名称，例如 600519、600519.SH、贵州茅台。传 code 时查询该股票异动状态。
dateNo交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传 code 时按日期扫描全市场。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, setting a low bar. The description adds genuinely useful behavioral context absent from annotations: automatic threshold differences by board type and automatic switching of the 主板风险警示口径 by rule effective date. It does not mention rate limits or data freshness, but the board-switching detail is a meaningful addition.

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 rule sentence is dense and front-loaded, but the trailing 【链接】 instruction about markdown link formatting is a presentation rule rather than tool semantics, and the description packs regulatory exceptions into one long sentence that risks losing the agent's attention.

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 annotations covering safety and an output schema covering return values, the description supplies the domain-specific rule knowledge (thresholds, board differentiation, effective-date switching) that an agent cannot infer from structured fields. It is complete enough for correct invocation, though sibling disambiguation is still 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%, and the schema itself documents code/date/format/detailLevel and the requirement of at least one of date/code. The description adds no parameter-level detail beyond the schema, so baseline 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?

The description states a specific verb and resource (按交易所规则检测个股价格偏离基准指数的异动) and details the exact detection thresholds (±20%/±30% for 主板/双创, 10日严重异动). This precisely distinguishes it from price-movement siblings like limit_up_filter or approaching_limit_up.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides a '何时使用' tag pointing to 监管口径异动和风险提示, but does not contrast with any of the numerous sibling tools (e.g., limit_events, broken_limit_up) or specify when *not* to use it. Usage context is implied rather than explicitly routed.

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