Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

nav_daily

Retrieve daily net asset value data for investment portfolios on Xueqiu. Use this tool to track portfolio performance by providing a cube symbol.

Instructions

获取组合净值数据

Args:
    cube_symbol: 组合代码

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cube_symbolNoSZ000002

Implementation Reference

  • main.py:276-284 (handler)
    The main handler function for the 'nav_daily' tool. It is registered via the @mcp.tool() decorator and implements the tool logic by fetching data from the pysnowball library (ball.nav_daily) and processing it with process_data.
    @mcp.tool()
    def nav_daily(cube_symbol: str="SZ000002") -> dict:
        """获取组合净值数据
        
        Args:
            cube_symbol: 组合代码
        """
        result = ball.nav_daily(cube_symbol)
        return process_data(result)
  • main.py:34-62 (helper)
    Shared helper function called by the nav_daily handler (and all other tools) to process the raw data returned from the library, primarily converting timestamps to human-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-32 (helper)
    Supporting utility function used by process_data to recursively convert timestamp fields in the data to formatted datetime strings.
    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
  • main.py:276-276 (registration)
    The @mcp.tool() decorator registers the nav_daily function as an MCP tool.
    @mcp.tool()
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. It mentions the action ('获取') but does not disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, error handling, or the format of returned data. This is a significant gap for a tool with no structured safety hints.

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 brief and front-loaded with the purpose, followed by parameter details. It avoids unnecessary verbosity, but the structure could be improved by integrating the parameter explanation more seamlessly rather than as a separate 'Args' section.

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 no annotations, no output schema, and low schema description coverage, the description is incomplete. It lacks details on return values, error conditions, and behavioral context, making it inadequate for safe and effective use by an AI agent without additional assumptions.

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 description includes an 'Args' section that lists 'cube_symbol: 组合代码', adding meaning by specifying that the parameter is a portfolio code. With 0% schema description coverage and 1 parameter, this partially compensates, but it does not explain the parameter's format, constraints, or the default value ('SZ000002') shown in the schema.

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 portfolio net value data), which provides a clear verb ('获取') and resource ('组合净值数据'), establishing the basic purpose. However, it does not differentiate this tool from sibling tools like 'fund_nav_history' or 'fund_detail', which might also retrieve net asset value data, leaving ambiguity about its specific scope.

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 offers no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'fund_nav_history', 'fund_detail', 'balance'), there is no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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