Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

sec_company_facts

Read-onlyIdempotent

查询 SEC companyfacts XBRL 财务事实，支持 Revenues、NetIncomeLoss、Assets、EarningsPerShareDiluted 等 us-gaap/dei tags。用于美股财报事实核验。 何时使用: SEC companyfacts：按 ticker/CIK 查询 XBRL 财务事实，如 Revenues、NetIncomeLoss、Assets、EarningsPerShareDiluted。适合美股财报事实核验。

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK，支持带或不带前导 0，例如 0001045810。与 ticker/query 任传其一。
tagNo单个 XBRL tag，例如 Revenues、RevenueFromContractWithCustomerExcludingAssessedTax、NetIncomeLoss、Assets、EarningsPerShareDiluted。
tagsNo多个 XBRL tag。不传则返回常用财务事实。
unitNo可选。单位筛选，例如 USD、shares、USD/shares。不传返回该 tag 所有单位。
limitNo返回事实条数，默认 20，最大 80。
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

C2.9/5.0
Behavior3/5

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

Annotations already carry the full safety profile (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds useful context about supported tag families and the fact-verification use case, but says nothing about rate limits, data freshness, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description repeats its core content nearly verbatim: the tag list (Revenues, NetIncomeLoss, Assets, EarningsPerShareDiluted) and the '美股财报事实核验' purpose appear twice. The second half is essentially filler rather than earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a rich output schema and complete parameter schema, most context is covered structurally, but the description wastes its budget on redundancy and omits the one thing only it could provide: when to prefer this over sec_filings / sec_company_search. Adequate but with a clear gap.

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% — cik, tag, tags, unit, limit, query, ticker, format and detailLevel are all documented in the schema itself. The description's tag examples merely duplicate the schema's own examples, adding no new parameter meaning. Baseline 3 is correct.

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 verb and resource ('查询 SEC companyfacts XBRL 财务事实') and scopes it to us-gaap/dei tags for US-stock financial fact verification. An agent can grasp what it does, though it never names the sibling it differs from (sec_filings, sec_company_search).

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

Usage Guidelines2/5

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

There is a literal '何时使用' (when to use) header, but its content simply restates the purpose — '按 ticker/CIK 查询 XBRL 财务事实' — with the same tag list. No when-not conditions, prerequisites, or alternatives (e.g. sec_filings for raw documents) are given.

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