Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

cash_flow

Retrieve cash flow statement data for specific stocks from the Xueqiu MCP server to analyze financial liquidity and operational performance.

Instructions

获取现金流量表数据

Args:
    stock_code: 股票代码
    is_annals: 只获取年报,默认为1
    count: 返回数据数量,默认5条

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stock_codeNoSZ000002
is_annalsNo
countNo

Implementation Reference

  • main.py:180-190 (handler)
    The handler function for the 'cash_flow' tool. It is decorated with @mcp.tool() for registration, fetches cash flow data from the pysnowball library (ball.cash_flow), processes the data using process_data helper, and returns it as a dict.
    @mcp.tool()
    def cash_flow(stock_code: str="SZ000002", is_annals: int = 1, count: int = 5) -> dict:
        """获取现金流量表数据
        
        Args:
            stock_code: 股票代码
            is_annals: 只获取年报,默认为1
            count: 返回数据数量,默认5条
        """
        result = ball.cash_flow(symbol=stock_code, is_annals=is_annals, count=count)
        return process_data(result)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves data ('获取'), implying a read-only operation, but doesn't disclose important behavioral aspects like data source, freshness, format of returned data, error conditions, or rate limits. For a financial data tool with no annotations, this leaves significant gaps in understanding how it behaves.

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?

The description is appropriately concise with a clear purpose statement followed by parameter explanations. Each sentence serves a purpose: the first states what the tool does, and the subsequent lines explain each parameter. No wasted words, though the structure could be slightly improved with clearer formatting.

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?

For a financial data retrieval tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the returned cash flow data looks like (structure, fields, time periods), data currency, source reliability, or typical use cases. The parameter explanations help, but significant context about the tool's behavior and output is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides meaningful parameter explanations that compensate well. It clarifies that 'stock_code' is a stock code, 'is_annals' controls whether to get only annual reports (with default 1), and 'count' specifies the number of data items to return (default 5). This adds substantial value beyond the bare schema fields.

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

Purpose3/5

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

The description states '获取现金流量表数据' (get cash flow statement data), which is a clear verb+resource combination. However, it doesn't distinguish this tool from potential siblings like 'balance' or 'income' that might provide other financial statements. The purpose is understandable but lacks differentiation.

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?

No guidance is provided about when to use this tool versus alternatives. With siblings like 'balance' and 'income' that likely provide other financial statements, the description offers no context about when cash flow data is needed versus balance sheet or income statement data. The only usage hint is implicit through parameter descriptions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/liqiongyu/xueqiu_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server