Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

index_details_data

Retrieve detailed information about stock market indices by providing the index code, enabling users to access comprehensive financial data through the Xueqiu MCP server.

Instructions

获取指数详细信息

Args:
    index_code: 指数代码

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
index_codeNoSZ000002

Implementation Reference

  • main.py:322-330 (handler)
    Handler function for the 'index_details_data' MCP tool. It fetches index details data using pysnowball library and processes timestamps before returning.
    def index_details_data(index_code: str="SZ000002") -> dict:
        """获取指数详细信息
        
        Args:
            index_code: 指数代码
        """
        result = ball.index_details_data(index_code)
        return process_data(result)
  • main.py:322-330 (registration)
    The @mcp.tool() decorator registers this function as an MCP tool named 'index_details_data'.
    def index_details_data(index_code: str="SZ000002") -> dict:
        """获取指数详细信息
        
        Args:
            index_code: 指数代码
        """
        result = ball.index_details_data(index_code)
        return process_data(result)
  • main.py:34-61 (helper)
    Helper function used by the tool to process the raw data, converting timestamps to readable format.
    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 helper recursively converts timestamp fields in the data to datetime strings, used 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. While '获取' (get) implies a read operation, the description doesn't address important behavioral aspects like whether this requires authentication, rate limits, what format the details are returned in, or potential error conditions. The description is too minimal to adequately inform an agent about how this tool 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 extremely concise with just two lines - a purpose statement and parameter documentation. While this is efficient, the parameter documentation could be better integrated rather than appearing as a separate 'Args:' section. There's no wasted text, but the structure feels slightly disjointed.

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 tool with no annotations, no output schema, and multiple similar sibling tools, the description is inadequate. It doesn't explain what '详细信息' (detailed information) includes, how it differs from other index tools, what the return format looks like, or any behavioral constraints. The minimal description leaves too many questions unanswered for effective agent 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 description explicitly documents the single parameter 'index_code' with a brief explanation, which adds value beyond the schema's 0% description coverage. However, it doesn't provide additional context about valid index code formats, examples beyond the default, or what happens if an invalid code is provided. The parameter documentation is minimal but exists.

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 as '获取指数详细信息' (get index details/information), which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'index_basic_info' or 'index_perf_30', leaving some ambiguity about what specific details this provides versus those other index-related tools.

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 multiple sibling tools related to indices (index_basic_info, index_perf_30, index_perf_7, index_perf_90, index_weight_top10), there's no indication of what distinguishes this tool's functionality from those others or when each should be selected.

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