Skip to main content
Glama

wmshare_statement

Fetches income, balance sheet, cash flow statements, key indicators, or audit opinions for CN, HK, and US listed companies by symbol, with configurable report periods and condensed output options.

Instructions

取三大报表(cn/hk/us 宽表)或审计意见。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "wmshare_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNo报表期数
actionYes报表动作
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolNo标的代码;所有 action 都需要
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "income",
      -  "balance",
      -  "cashflow",
      -  "audit",
      -  "compare",
      -  "tree",
      -  "years"
      -]New value: +[
      +  "income",
      +  "balance",
      +  "cashflow",
      +  "indicators",
      +  "audit"
      +]
    • removedInput schema / properties / kind
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "enum": [
      -        "income",
      -        "balance",
      -        "cashflow"
      -      ],
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": "income",
      -  "description": "compare/tree/years 使用的报表类型",
      -  "title": "Kind"
      -}
    • removedInput schema / properties / scope
      Removed value: -{
      -  "default": "合并",
      -  "description": "报表口径:合并或母公司",
      -  "enum": [
      -    "合并",
      -    "母公司"
      -  ],
      -  "title": "Scope",
      -  "type": "string"
      -}
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and does very little with it: it never states that this is a read-only fetch, never mentions the default market from server config, the 5-period default, or the hard 200-row cap that constrains how results come back. Only the 取 verb implies a non-mutating read.

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

Conciseness4/5

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

A single short sentence with the resource and market scope front-loaded and no filler. It is efficient, though the terseness borders on under-specification rather than crispness.

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

Completeness3/5

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

With an output schema present and full schema descriptions, the description needn't explain return shapes, so the remaining burden is modest. Still, for a six-parameter tool with two enums, leaving out the 'indicators' action and any routing guidance leaves an agent with gaps the structured fields don't close.

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 the schema already documents all six parameters and the baseline is 3. The description does add a small mapping (三大报表 → income/balance/cashflow, 审计意见 → audit) but omits the 'indicators' action entirely and says nothing about years, output mode, or symbol requirements.

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 gives a specific verb (取/fetch) and resource (三大报表 / 审计意见), plus the market dimension (cn/hk/us 宽表), so an agent knows this is the financial-statements tool rather than a quote, dividend, or estimate tool. It stops short of naming a sibling or stating what it is not, so it lands at 4 rather than 5.

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 no when-to-use or when-not-to-use guidance, and no alternative tool is mentioned among the 19 siblings (e.g. wmshare_metrics, wmshare_company). The '或审计意见' clause only hints that an audit mode exists; it does not tell the agent which conditions should drive that choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.