Skip to main content
Glama
Sign In
AkTools MCP Server

AkTools MCP Server

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

A股关键指标

stock_indicators_a

Get key financial report indicators for Chinese A-share stocks (Shanghai, Shenzhen) by providing a stock code.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "stock_indicators_a"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes股票代码

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.14

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the basic function and market scope, without mentioning data source, update frequency, potential limitations, or any other behavioral characteristics. The description adds minimal context beyond the title.

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?

The description is a single, concise sentence that front-loads the essential information: what the tool does and its market scope. There is no redundant or filler content.

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?

With only one parameter and no output schema, the description is fairly simple. However, it does not clarify what 'key indicators' are included, which could be important for an agent deciding whether to use this tool. The absence of an output schema increases the need for such detail, making the description only minimally viable.

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% because the 'symbol' parameter has the description '股票代码' (stock code). The tool description adds no additional parameter semantics beyond the schema, so a baseline of 3 is appropriate.

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 uses a specific verb '获取' (retrieve) and a clear resource '股票财务报告关键指标' (key financial report indicators). It explicitly scopes to China's A-share market (Shanghai, Shenzhen), which distinguishes it from sibling tools like stock_indicators_hk and stock_indicators_us. The purpose is unambiguous.

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

Usage Guidelines3/5

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

The description implies usage for A-share stocks by specifying the market, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. No alternative tools are referenced. Usage is inferred rather than articulated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools