Skip to main content
Glama
24mlight

A Share MCP

get_sz50_stocks

Retrieve the current constituents of the SZSE 50 index to analyze top-performing A-share stocks listed on the Shenzhen Stock Exchange.

Instructions

SZSE 50 constituents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
limitNo
formatNomarkdown

Implementation Reference

  • Primary MCP tool handler for 'get_sz50_stocks'. Registered via @app.tool() decorator. Delegates execution to the use-cases layer via run_tool_with_handling.
    @app.tool()
    def get_sz50_stocks(date: Optional[str] = None, limit: int = 250, format: str = "markdown") -> str:
        """SZSE 50 constituents."""
        return run_tool_with_handling(
            lambda: fetch_index_constituents(active_data_source, index="sz50", date=date, limit=limit, format=format),
            context="get_sz50_stocks",
        )
  • mcp_server.py:51-58 (registration)
    Registration block in main server file where register_index_tools is called to register the index tools including get_sz50_stocks.
    register_stock_market_tools(app, active_data_source)
    register_financial_report_tools(app, active_data_source)
    register_index_tools(app, active_data_source)
    register_market_overview_tools(app, active_data_source)
    register_macroeconomic_tools(app, active_data_source)
    register_date_utils_tools(app, active_data_source)
    register_analysis_tools(app, active_data_source)
    register_helpers_tools(app)
  • Use case helper function invoked by the tool handler. Routes 'sz50' requests to data_source.get_sz50_stocks() and formats the output.
    def fetch_index_constituents(data_source: FinancialDataSource, *, index: str, date: Optional[str], limit: int, format: str) -> str:
        validate_output_format(format)
        key = validate_index_key(index, INDEX_MAP)
        if key == "hs300":
            df = data_source.get_hs300_stocks(date=date)
        elif key == "sz50":
            df = data_source.get_sz50_stocks(date=date)
        else:
            df = data_source.get_zz500_stocks(date=date)
        meta = {"index": key, "as_of": date or "latest"}
        return format_table_output(df, format=format, max_rows=limit, meta=meta)
  • Concrete data source implementation for fetching SZSE 50 stocks using Baostock API via helper function.
    def get_sz50_stocks(self, date: Optional[str] = None) -> pd.DataFrame:
        """Fetches SZSE 50 index constituents using Baostock."""
        return _fetch_index_constituent_data(bs.query_sz50_stocks, "SZSE 50", date)
  • Shared helper function in BaostockDataSource used by get_sz50_stocks to query and process Baostock API response.
    def _fetch_index_constituent_data(
        bs_query_func,
        index_name: str,
        date: Optional[str] = None
    ) -> pd.DataFrame:
        logger.info(
            f"Fetching {index_name} constituents for date={date or 'latest'}")
        try:
            with baostock_login_context():
                # date is optional, defaults to latest
                rs = bs_query_func(date=date)
    
                if rs.error_code != '0':
                    logger.error(
                        f"Baostock API error ({index_name} Constituents) for date {date}: {rs.error_msg} (code: {rs.error_code})")
                    if "no record found" in rs.error_msg.lower() or rs.error_code == '10002':
                        raise NoDataFoundError(
                            f"No {index_name} constituent data found for date {date}. Baostock msg: {rs.error_msg}")
                    else:
                        raise DataSourceError(
                            f"Baostock API error fetching {index_name} constituents: {rs.error_msg} (code: {rs.error_code})")
    
                data_list = []
                while rs.next():
                    data_list.append(rs.get_row_data())
    
                if not data_list:
                    logger.warning(
                        f"No {index_name} constituent data found for date {date} (empty result set).")
                    raise NoDataFoundError(
                        f"No {index_name} constituent data found for date {date} (empty result set).")
    
                result_df = pd.DataFrame(data_list, columns=rs.fields)
                logger.info(
                    f"Retrieved {len(result_df)} {index_name} constituents for date {date or 'latest'}.")
                return result_df
    
        except (LoginError, NoDataFoundError, DataSourceError, ValueError) as e:
            logger.warning(
                f"Caught known error fetching {index_name} constituents for date {date}: {type(e).__name__}")
            raise e
        except Exception as e:
            logger.exception(
                f"Unexpected error fetching {index_name} constituents for date {date}: {e}")
            raise DataSourceError(
                f"Unexpected error fetching {index_name} constituents for date {date}: {e}")
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. It doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. The description is minimal and fails to add meaningful context beyond the tool name.

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 a single phrase, which is front-loaded and wastes no words. However, it may be overly terse, bordering on under-specification, but it's structured efficiently 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 complexity (3 parameters with 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain what the tool returns, how parameters influence results, or behavioral aspects. For a data retrieval tool with multiple parameters, this is inadequate.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It provides no information about the three parameters (date, limit, format), their purposes, or how they affect the output. This leaves significant gaps in understanding parameter usage.

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 'SZSE 50 constituents' clearly indicates the resource (SZSE 50 index constituents) but lacks a specific verb. It distinguishes from some siblings like 'get_hs300_stocks' or 'get_zz500_stocks' by specifying which index, but doesn't clarify the action (e.g., retrieve, list, fetch). This makes the purpose somewhat vague but not tautological.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention siblings like 'get_hs300_stocks' for different indices or 'get_index_constituents' for general index data, nor does it specify prerequisites or exclusions. The description alone offers no usage context.

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/24mlight/a_share_mcp_is_just_I_need'

If you have feedback or need assistance with the MCP directory API, please join our Discord server