Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

sec_filings

Read-onlyIdempotent

查询美国上市公司最近 SEC filings，支持 10-K、10-Q、8-K、DEF 14A、Form 4、13F-HR 等表单过滤，并返回 SEC 官方 filing URL。 何时使用: SEC filings 列表：按 ticker 或 CIK 查询 10-K/10-Q/8-K/DEF 14A/Form 4 等最近披露，并返回官方 filing URL。适合海外公司披露核验和 A 股海外映射。

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK，支持带或不带前导 0，例如 0001045810。与 ticker/query 任传其一。
formNo可选。披露表单类型，例如 10-K、10-Q、8-K、DEF 14A、4、13F-HR。不传返回全部最近 filing。
limitNo返回数量，默认 10，最大 50。
queryNo公司名或 ticker，无法确定 ticker 时传这里。与 ticker/cik 任传其一。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
tickerNo美股 ticker，例如 NVDA、AAPL、TSLA。与 cik/query 任传其一。
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

B3.4/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 covered. The description adds that an SEC-official filing URL is returned, but says nothing about SEC rate limits, freshness/latency of filings, pagination, or truncation behavior beyond what annotations and the output schema give.

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 leading sentence is well front-loaded (verb, resource, form list, returned URL), but the '何时使用' block repeats the same form-type enumeration and query-by-ticker/CIK point nearly verbatim, so a meaningful share of the text is redundancy rather than new 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?

With an output schema present, annotations covering safety, and 100% schema coverage on all 7 parameters, the definition only needs to frame what the tool returns and when to reach for it — both of which it does. It stops short of 5 because it leaves the agent without any signal on how it differs from the SEC-related siblings.

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 (cik, ticker, query, form, limit, format, detailLevel) is already documented in the schema, including the at-least-one-of constraint. The description's mention of form types and the ticker/CIK lookup path adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

The description names a specific verb (查询/list) and resource (US listed companies' recent SEC filings), enumerates supported form types (10-K, 10-Q, 8-K, DEF 14A, Form 4, 13F-HR), and states that an official filing URL is returned. It is clear, though it never distinguishes itself from close siblings like sec_company_facts, sec_company_search, or official_disclosure_evidence.

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?

A dedicated '何时使用' clause tells the agent to use this when it needs a filing list by ticker or CIK, and adds a domain note about overseas disclosure verification and A-share overseas mapping. However, that clause largely repeats the opening sentence and offers no when-not guidance or comparison against the obviously overlapping sec_company_search/sec_company_facts siblings.

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