Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

earningforecast

Retrieve annual earnings forecast data for specific stocks to analyze company performance projections and inform investment decisions.

Instructions

按年度获取业绩预告数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stock_codeNoSZ000002

Implementation Reference

  • main.py:92-96 (handler)
    The main handler function for the 'earningforecast' MCP tool. Decorated with @mcp.tool() for registration. Calls pysnowball.ball.earningforecast(stock_code), processes the result with process_data(), and returns a dict.
    @mcp.tool()
    def earningforecast(stock_code: str="SZ000002") -> dict:
        """按年度获取业绩预告数据"""
        result = ball.earningforecast(stock_code)
        return process_data(result)
  • main.py:93-94 (schema)
    Input/output schema defined by function signature: stock_code (str, default 'SZ000002') -> dict. Docstring: 'Get performance forecast data by year'.
    def earningforecast(stock_code: str="SZ000002") -> dict:
        """按年度获取业绩预告数据"""
  • main.py:34-61 (helper)
    Helper utility for processing raw data from pysnowball APIs. By default converts timestamps to readable datetime strings. Used by all tools including earningforecast.
    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 recursive function to convert timestamp fields (and _date fields) in nested data structures to formatted datetime strings. Called by process_data.
    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 for behavioral disclosure. It only states what data is retrieved ('业绩预告数据') without mentioning any behavioral traits like whether this requires authentication, has rate limits, returns structured or raw data, includes error handling, or what time periods are covered. For a data retrieval tool with zero 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.

Conciseness5/5

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

The description is extremely concise—a single phrase in Chinese—with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying the essential purpose without redundancy.

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?

Given the tool's complexity (data retrieval with a parameter), lack of annotations, no output schema, and low parameter documentation, the description is incomplete. It doesn't address what the output contains (e.g., forecast values, dates, confidence intervals), how results are structured, or any prerequisites. For a financial data tool, this leaves significant gaps for an AI agent to use it correctly.

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

Parameters2/5

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

The input schema has 1 parameter with 0% description coverage (only title 'Stock Code' and default 'SZ000002'). The description adds no semantic information about parameters—it doesn't explain what 'stock_code' represents, valid formats, or how it affects the output. With low schema coverage, the description fails to compensate, leaving the parameter poorly documented.

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 '按年度获取业绩预告数据' (Get annual earnings forecast data) states a clear verb ('获取' - get) and resource ('业绩预告数据' - earnings forecast data), but it's vague about scope and granularity. It doesn't specify whether this returns historical forecasts, future projections, or both, nor how it differs from siblings like 'income' or 'report' which might contain related financial data.

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 many sibling tools (e.g., 'income', 'report', 'indicator') that could overlap with financial data, there's no indication of when this specific earnings forecast data is preferred or what distinguishes it from other financial reporting 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