Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

income

Retrieve income statement data for specific stocks from Xueqiu MCP, enabling analysis of financial performance with customizable parameters for reporting periods and data quantity.

Instructions

获取利润表数据

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stock_codeNoSZ000002
is_annalsNo
countNo

Implementation Reference

  • main.py:154-164 (handler)
    The handler function for the 'income' MCP tool. It is decorated with @mcp.tool() for automatic registration. Fetches profit table data from pysnowball library (ball.income) and processes the result with timestamp conversion.
    @mcp.tool()
    def income(stock_code: str="SZ000002", is_annals: int = 1, count: int = 5) -> dict:
        """获取利润表数据
        
        Args:
            stock_code: 股票代码
            is_annals: 只获取年报,默认为1
            count: 返回数据数量,默认5条
        """
        result = ball.income(symbol=stock_code, is_annals=is_annals, count=count)
        return process_data(result)
  • main.py:154-154 (registration)
    The @mcp.tool() decorator registers the 'income' function as an MCP tool.
    @mcp.tool()
  • main.py:34-61 (helper)
    Helper function used by the 'income' tool (and others) to process the raw data, converting timestamps to readable datetime strings.
    def process_data(data, process_config=None):
        """
        通用数据处理函数,可扩展添加各种数据处理操作
        
        Args:
            data: 原始数据
            process_config: 处理配置字典,用于指定要执行的处理操作
                例如: {'convert_timestamps': True, 'other_process': params}
        
        Returns:
            处理后的数据
        """
        if process_config is None:
            # 默认配置
            process_config = {
                'convert_timestamps': True
            }
        
        # 如果开启了时间戳转换
        if process_config.get('convert_timestamps', True):
            data = convert_timestamps(data)
        
        # 在这里可以添加更多的数据处理逻辑
        # 例如:
        # if 'format_numbers' in process_config:
        #     data = format_numbers(data, **process_config['format_numbers'])
        
        return data
  • main.py:14-31 (helper)
    Supporting utility for recursive timestamp conversion in data processing, used indirectly by the 'income' tool.
    def convert_timestamps(data):
        """递归地将数据中的所有 timestamp 转换为 datetime 字符串"""
        if isinstance(data, dict):
            for key, value in list(data.items()):
                if key == 'timestamp' and isinstance(value, (int, float)) and value > 1000000000000:  # 毫秒级时间戳
                    data[key] = datetime.datetime.fromtimestamp(value/1000).strftime('%Y-%m-%d %H:%M:%S')
                elif key == 'timestamp' and isinstance(value, (int, float)) and value > 1000000000:  # 秒级时间戳
                    data[key] = datetime.datetime.fromtimestamp(value).strftime('%Y-%m-%d %H:%M:%S')
                elif key.endswith('_date') and isinstance(value, (int, float)) and value > 1000000000000:  # 毫秒级时间戳
                    data[key] = datetime.datetime.fromtimestamp(value/1000).strftime('%Y-%m-%d %H:%M:%S')
                elif key.endswith('_date') and isinstance(value, (int, float)) and value > 1000000000:  # 秒级时间戳
                    data[key] = datetime.datetime.fromtimestamp(value).strftime('%Y-%m-%d %H:%M:%S')
                elif isinstance(value, (dict, list)):
                    data[key] = convert_timestamps(value)
        elif isinstance(data, list):
            for i, item in enumerate(data):
                data[i] = convert_timestamps(item)
        return data
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 mentions the tool '获取' (gets/retrieves) data, implying a read-only operation, but doesn't disclose important behavioral aspects like authentication requirements, rate limits, data freshness, error conditions, or response format. For a financial data tool with no annotation coverage, this is insufficient.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence serves a purpose: the first states what the tool does, and the subsequent lines document each parameter with default values. There's no wasted text.

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 income statement data looks like (structure, fields, time periods), doesn't mention data sources or reliability, and provides no error handling context. The parameter explanations help, but overall context is lacking.

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 compensates well by explaining all three parameters in Chinese: 'stock_code: 股票代码' (stock code), 'is_annals: 只获取年报,默认为1' (only get annual reports, default is 1), and 'count: 返回数据数量,默认5条' (return data count, default 5 items). This adds crucial semantic meaning beyond the schema's minimal titles.

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 clearly states the tool's purpose: '获取利润表数据' (Get income statement data). It specifies the verb ('获取' - get) and resource ('利润表数据' - income statement data), making the function unambiguous. However, it doesn't differentiate from sibling tools like 'balance' or 'cash_flow', which likely provide different financial statements.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'balance' (likely for balance sheet data) and 'cash_flow' (likely for cash flow statement data), there's no indication of when income statement data is specifically needed or how this tool relates to other financial data tools.

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