Skip to main content
Glama
al-one

MCP Server for stock and crypto

A股涨停股池

stock_zt_pool_em

Retrieves all stocks that hit the daily price limit (涨停) in China's A-share markets, with optional date and count parameters.

Instructions

获取中国A股市场(上证、深证)的所有涨停股票

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo交易日日期(可选),默认为最近的交易日,格式: 20251231
limitNo返回数量(int,30-100)

Implementation Reference

  • The function that executes the stock_zt_pool_em tool logic: fetches the daily limit-up (涨停) stock pool from akshare, drops unnecessary columns, sorts by turnover amount, limits results, and returns as CSV text.
    def stock_zt_pool_em(
        date: str = Field("", description="交易日日期(可选),默认为最近的交易日,格式: 20251231"),
        limit: int = Field(50, description="返回数量(int,30-100)", strict=False),
    ):
        if not date:
            date = recent_trade_date().strftime("%Y%m%d")
        dfs = ak_cache(ak.stock_zt_pool_em, date=date, ttl=1200)
        cnt = len(dfs)
        try:
            dfs.drop(columns=["序号", "流通市值", "总市值"], inplace=True)
        except Exception:
            pass
        dfs.sort_values("成交额", ascending=False, inplace=True)
        dfs = dfs.head(int(limit))
        desc = f"共{cnt}只涨停股\n"
        return desc + dfs.to_csv(index=False, float_format="%.2f").strip()
  • Registration of stock_zt_pool_em as an MCP tool using the @mcp.tool decorator with title and description metadata.
    @mcp.tool(
        title="A股涨停股池",
        description="获取中国A股市场(上证、深证)的所有涨停股票",
    )
  • Input parameter schema for stock_zt_pool_em: date (optional string) and limit (int, default 50, range 30-100).
        date: str = Field("", description="交易日日期(可选),默认为最近的交易日,格式: 20251231"),
        limit: int = Field(50, description="返回数量(int,30-100)", strict=False),
    ):
  • Helper function to find the most recent trading date, used when no date is provided to stock_zt_pool_em.
    def recent_trade_date():
        now = datetime.now().date()
        dfs = ak_cache(ak.tool_trade_date_hist_sina, ttl=43200)
        if dfs is None:
            return now
        dfs.sort_values("trade_date", ascending=False, inplace=True)
        for d in dfs["trade_date"]:
            if d <= now:
                return d
        return now
  • Helper caching function that wraps akshare API calls with in-memory and disk caching (TTL-based), used to call ak.stock_zt_pool_em with a 1200-second TTL cache.
    def ak_cache(fun, *args, **kwargs) -> pd.DataFrame | None:
        key = kwargs.pop("key", None)
        if not key:
            key = f"{fun.__name__}-{args}-{kwargs}"
        ttl1 = kwargs.pop("ttl", 86400)
        ttl2 = kwargs.pop("ttl2", None)
        cache = CacheKey.init(key, ttl1, ttl2)
        all = cache.get()
        if all is None:
            try:
                _LOGGER.info("Request akshare: %s", [key, args, kwargs])
                all = fun(*args, **kwargs)
                cache.set(all)
            except Exception as exc:
                _LOGGER.exception(str(exc))
        return all
Behavior2/5

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

No annotations are present, so the description should fully disclose behavior. It only states the action but does not mention rate limits, authentication requirements, or what happens if no data exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Description is a single, clear sentence with no unnecessary words. It effectively communicates the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should hint at return format or data structure. It does not. However, with only two simple parameters, it is minimally adequate.

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?

Both parameters are fully described in the input schema, and the description adds no additional meaning. The schema coverage is 100%, so a baseline score of 3 is appropriate.

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?

Description clearly states the tool retrieves all limit-up stocks in China A-share market (Shanghai, Shenzhen). The verb '获取' and resource '涨停股票' are explicit. However, it does not differentiate from the sibling tool stock_zt_pool_strong_em.

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 on when to use this tool versus alternatives, such as stock_zt_pool_strong_em. No prerequisites or contextual hints provided.

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/al-one/mcp-aktools'

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