Skip to main content
Glama
al-one

MCP Server for stock and crypto

查找股票代码

search

Find stock codes by entering company name, stock name, or keyword for Shanghai, Shenzhen, Hong Kong, or US markets. Does not support cryptocurrency.

Instructions

根据股票名称、公司名称等关键词查找股票代码, 不支持加密货币。该工具比较耗时,当你知道股票代码或用户已指定股票代码时,建议直接通过股票代码使用其他工具

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes搜索关键词,公司名称、股票名称、股票代码、证券简称
marketNo股票市场,仅支持: sh(上证), sz(深证), hk(港股), us(美股), 不支持加密货币sh

Implementation Reference

  • Main handler function for the 'search' MCP tool. Decorated with @mcp.tool, accepts keyword and market parameters, delegates to ak_search() helper, and formats the result.
    @mcp.tool(
        title="查找股票代码",
        description="根据股票名称、公司名称等关键词查找股票代码, 不支持加密货币。"
                    "该工具比较耗时,当你知道股票代码或用户已指定股票代码时,建议直接通过股票代码使用其他工具",
    )
    def search(
        keyword: str = Field(description="搜索关键词,公司名称、股票名称、股票代码、证券简称"),
        market: str = field_market,
    ):
        info = ak_search(None, keyword, market)
        if info is not None:
            suffix = f"交易市场: {market}"
            return "\n".join([info.to_string(), suffix])
        return f"Not Found for {keyword}"
  • Input schema for the search tool: keyword (required string) and market (optional, defaults to 'sh').
    keyword: str = Field(description="搜索关键词,公司名称、股票名称、股票代码、证券简称"),
    market: str = field_market,
  • Helper function that searches across multiple markets (SH, SZ, HK, US) using akshare APIs. Supports exact code match, keyword match (code or name), substring match (keyword length >= 4), and prefix match.
    def ak_search(symbol=None, keyword=None, market=None):
        markets = [
            ["sh", ak.stock_info_a_code_name, "code", "name"],
            ["sh", ak.stock_info_sh_name_code, "证券代码", "证券简称"],
            ["sz", ak.stock_info_sz_name_code, "A股代码", "A股简称"],
            ["hk", ak.stock_hk_spot, "代码", "中文名称"],
            ["hk", ak.stock_hk_spot_em, "代码", "名称"],
            ["us", ak.get_us_stock_name, "symbol", "cname"],
            ["us", ak.get_us_stock_name, "symbol", "name"],
            ["sh", ak.fund_etf_spot_ths, "基金代码", "基金名称"],
            ["sz", ak.fund_etf_spot_ths, "基金代码", "基金名称"],
            ["sh", ak.fund_info_index_em, "基金代码", "基金名称"],
            ["sz", ak.fund_info_index_em, "基金代码", "基金名称"],
            ["sh", ak.fund_etf_spot_em, "代码", "名称"],
            ["sz", ak.fund_etf_spot_em, "代码", "名称"],
        ]
        for m in markets:
            if market and market != m[0]:
                continue
            all = ak_cache(m[1], ttl=86400, ttl2=86400*7)
            if all is None or all.empty:
                continue
            for _, v in all.iterrows():
                code, name = str(v[m[2]]).upper(), str(v[m[3]]).upper()
                if symbol and symbol.upper() == code:
                    return v
                if keyword and keyword.upper() in [code, name]:
                    return v
            for _, v in all.iterrows() if keyword else []:
                name = str(v[m[3]])
                if len(keyword) >= 4 and keyword in name:
                    return v
                if name.startswith(keyword):
                    return v
        return None
  • Caching helper that wraps akshare API calls with a two-level cache (in-memory TTL cache + disk cache) to avoid redundant network requests.
    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
  • Registration of the 'search' tool via the @mcp.tool decorator on the FastMCP instance, with title '查找股票代码'.
    @mcp.tool(
        title="查找股票代码",
        description="根据股票名称、公司名称等关键词查找股票代码, 不支持加密货币。"
                    "该工具比较耗时,当你知道股票代码或用户已指定股票代码时,建议直接通过股票代码使用其他工具",
Behavior3/5

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

With no annotations provided, the description adds the behavioral note that the tool is time-consuming. However, it lacks details on edge cases (e.g., no match, invalid market) or return behavior, which would be expected for a search tool.

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?

Two concise sentences: the first states the purpose and the second provides usage guidance. No unnecessary words, and key information is front-loaded.

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?

The tool is simple with two parameters and no output schema. The description covers the primary purpose and a key behavioral trait (time-consuming) but does not explain the return format or pagination, leaving some ambiguity for the agent.

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?

Schema coverage is 100%, so the baseline is 3. The description adds minimal new meaning beyond the schema: it reiterates that keyword involves stock/company names and that market excludes crypto. No additional format or constraint details are provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: searching for stock codes using keywords like stock name or company name, and explicitly excludes cryptocurrency. It is specific and distinct from sibling tools, which focus on other operations like indicators or prices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: it notes the tool is time-consuming and advises using other tools directly when the stock code is already known. This helps the agent decide when to use this tool versus alternatives.

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