Skip to main content
Glama
al-one

MCP Server for stock and crypto

A股关键指标

stock_indicators_a

Retrieve key financial indicators for Chinese A-share market stocks (Shanghai, Shenzhen) to analyze company performance and make informed investment decisions.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes股票代码

Implementation Reference

  • The core handler function for the 'stock_indicators_a' tool. It fetches financial abstract data for the given A-share stock symbol using akshare's stock_financial_abstract_ths, caches it, formats as CSV, and returns the header plus the last 15 rows.
    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 registers the 'stock_indicators_a' tool with its title and description.
    @mcp.tool(
        title="A股关键指标",
        description="获取中国A股市场(上证、深证)的股票财务报告关键指标",
    )
  • Input schema definition for the tool parameter 'symbol', referencing the shared field_symbol which is a Pydantic Field for stock code.
    symbol: str = field_symbol,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it states this is a retrieval operation ('获取'), it doesn't describe what 'key indicators' include, whether there are rate limits, authentication requirements, data freshness, error conditions, or response format. For a financial data tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient Chinese sentence that clearly states the tool's purpose. It's appropriately sized for a simple retrieval tool with one parameter. While it could potentially be more front-loaded with critical information, there's no wasted verbiage or unnecessary complexity.

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?

For a financial data retrieval tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'key indicators' include, the response format, data sources, update frequency, or limitations. Given the complexity of financial data and the lack of structured output documentation, the description should provide more context about what users can expect from this tool.

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 description coverage is 100% with a single parameter 'symbol' documented as '股票代码' (stock code). The description doesn't add any parameter semantics beyond what the schema provides - it doesn't clarify format requirements (e.g., exchange prefixes), valid ranges, or examples. With complete schema coverage, the baseline is 3 even without additional parameter information in the description.

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: '获取中国A股市场(上证、深证)的股票财务报告关键指标' (Get key financial report indicators for Chinese A-share market stocks). It specifies the resource (A-share stocks), scope (Shanghai/Shenzhen exchanges), and what it retrieves (financial report key indicators). However, it doesn't explicitly differentiate from sibling tools like 'stock_indicators_hk' or 'stock_indicators_us', which would require a 5.

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. There are multiple sibling tools for stock indicators (HK, US) and related financial data (stock_info, stock_prices), but the description doesn't indicate when this A-share specific tool is appropriate versus other options. It simply states what it does without contextual usage information.

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