Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

capital_history

Retrieve historical capital flow data for Chinese stocks, including daily inflow and outflow metrics, to analyze market trends and investment patterns.

Instructions

获取历史资金流如流出数据,每日数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stock_codeNoSZ000002

Implementation Reference

  • main.py:113-117 (handler)
    The handler function for the 'capital_history' tool. It fetches historical capital flow data (daily) for a given stock code using the pysnowball library, processes timestamps, and returns the result as a dictionary.
    @mcp.tool()
    def capital_history(stock_code: str="SZ000002") -> dict:
        """获取历史资金流如流出数据,每日数据"""
        result = ball.capital_history(stock_code)
        return process_data(result)
  • main.py:113-113 (registration)
    The @mcp.tool() decorator registers the capital_history function as an MCP tool.
    @mcp.tool()
  • Function signature defines the input schema (stock_code: str with default) and output (dict), used by FastMCP for tool schema generation.
    def capital_history(stock_code: str="SZ000002") -> dict:
  • main.py:34-61 (helper)
    Helper function that processes the raw data from pysnowball, including converting timestamps to readable datetime strings. Used by all tools including capital_history.
    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 recursively converts timestamp fields in the data 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 the full burden of behavioral disclosure. It mentions retrieving daily data but does not specify aspects like data format, time range limits, authentication needs, rate limits, or whether it's a read-only operation. This is inadequate for a tool with no annotation coverage.

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 a single, efficient sentence that clearly states the purpose. It is front-loaded and avoids unnecessary words, making it easy to parse quickly.

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 complexity of financial data retrieval, no annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It lacks details on data scope, return format, and behavioral traits, making it incomplete for effective tool use.

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?

The input schema has one parameter ('stock_code') with 0% description coverage, and the tool description does not mention any parameters. Since there are no parameters described, the baseline is 4, but the description fails to compensate for the lack of schema coverage by explaining what 'stock_code' represents or its format, resulting in a score of 3.

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 the tool retrieves historical capital flow data (e.g., outflow) on a daily basis, which clarifies the verb ('获取' meaning 'get/retrieve') and resource ('历史资金流如流出数据' meaning 'historical capital flow such as outflow data'). However, it does not distinguish this tool from sibling tools like 'capital_flow' or 'capital_assort', leaving ambiguity about their specific differences.

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. It does not mention any prerequisites, exclusions, or comparisons to sibling tools such as 'capital_flow' or 'capital_assort', leaving the agent without context for selection.

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