Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

northbound_shareholding_sz

Retrieve northbound shareholding data for Shenzhen-listed stocks from the Shanghai-Hong Kong Stock Connect program. Query specific dates to access institutional investment flows.

Instructions

获取沪港通北向数据

Args:
    date: 日期,默认当天,格式:'2022/01/19'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo

Implementation Reference

  • main.py:387-395 (handler)
    The handler function decorated with @mcp.tool(), which registers and implements the northbound_shareholding_sz tool. It calls the pysnowball library's method and processes the result with timestamp conversion.
    @mcp.tool()
    def northbound_shareholding_sz(date: str = None) -> dict:
        """获取沪港通北向数据
        
        Args:
            date: 日期,默认当天,格式:'2022/01/19'
        """
        result = ball.northbound_shareholding_sz(date)
        return process_data(result)
  • main.py:34-61 (helper)
    Helper function used by the tool 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 recursively called by process_data to 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
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It only mentions the date parameter format but doesn't describe what the tool returns, whether it's a read-only operation, any rate limits, authentication requirements, or error conditions. 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.

Conciseness3/5

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

The description is appropriately brief but could be better structured. The purpose statement is clear, but the parameter documentation is presented in a somewhat informal 'Args:' format. While efficient, it lacks the polished structure of more formal documentation.

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 lack of annotations and output schema, the description is incomplete. It documents the single parameter adequately but fails to describe what data is returned, the format of results, or any behavioral characteristics. For a data retrieval tool, users need to know what to expect in response.

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?

The description adds significant value beyond the input schema, which has 0% description coverage. It explains the 'date' parameter's purpose (日期 - date), default behavior (默认当天 - defaults to current day), and format requirements (格式:'2022/01/19'). This compensates well for the schema's lack of documentation for the single parameter.

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 Northbound Stock Connect data), which specifies both the verb ('获取' - get) and resource ('沪港通北向数据' - Northbound Stock Connect data). It distinguishes from sibling tools like 'northbound_shareholding_sh' by specifying the Shenzhen exchange focus. However, it doesn't explicitly mention this is for shareholding data specifically.

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. While it distinguishes from 'northbound_shareholding_sh' by context, there's no explicit comparison or guidance about when to choose one over the other, nor any mention of prerequisites or typical use cases.

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