Skip to main content
Glama
al-one

MCP Server for stock and crypto

A股关键指标

stock_indicators_a

Retrieve key financial report indicators for Chinese A-share stocks from Shanghai and Shenzhen exchanges using a stock symbol.

Instructions

获取中国A股市场(上证、深证)的股票财务报告关键指标

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes股票代码

Implementation Reference

  • The handler function for the 'stock_indicators_a' tool. It calls ak_cache with ak.stock_financial_abstract_ths using the provided symbol, converts the result to CSV, and returns only the header row plus the last 15 rows of data.
    def stock_indicators_a(
        symbol: str = field_symbol,
    ):
        dfs = ak_cache(ak.stock_financial_abstract_ths, symbol=symbol)
        keys = dfs.to_csv(index=False, float_format="%.3f").strip().split("\n")
        return "\n".join([keys[0], *keys[-15:]])
  • The @mcp.tool decorator registering stock_indicators_a as an MCP tool with title 'A股关键指标' and description '获取中国A股市场(上证、深证)的股票财务报告关键指标'.
    @mcp.tool(
        title="A股关键指标",
        description="获取中国A股市场(上证、深证)的股票财务报告关键指标",
    )
  • The input parameter schema: 'symbol' is a string using the shared 'field_symbol' field descriptor (description: '股票代码').
        symbol: str = field_symbol,
    ):
  • The ak_cache helper function used by stock_indicators_a to cache and fetch data. It wraps akshare API calls with a two-layer cache (in-memory TTLCache + diskcache).
    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
Behavior3/5

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

No annotations are provided, so the description must fully convey behavior. It states it gets 'key indicators' but does not specify what those indicators are, whether data is real-time or historical, or any limitations.

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?

Single, concise sentence that efficiently communicates the tool's purpose without unnecessary words.

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

Completeness4/5

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

The tool is simple with one required parameter. The description is adequate for basic understanding, but lacks detail on the nature of the output (key indicators). Given no output schema, additional clarification would help.

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% with one parameter 'symbol' described as '股票代码'. The description adds no additional semantic meaning beyond what the schema provides.

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?

Description clearly states it fetches key financial report indicators for the Chinese A-share market, specifying Shanghai and Shenzhen exchanges. It implicitly distinguishes from sibling tools targeting Hong Kong and US markets.

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

Usage Guidelines4/5

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

Usage context is clear (A-share financial indicators). Sibling tool names provide implicit guidance, but no explicit when-to-use or when-not-to-use instructions are given.

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