A-share and HK stock data via AKShare: OHLCV history, current price, symbol search, index daily data.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Calendar days of history (default 365) | |
| action | Yes | ||
| adjust | No | Price adjustment: empty=none, qfq=forward, hfq=backward | |
| market | No | Market: a=A-share (default), hk=Hong Kong | |
| period | No | Period (default: daily) | |
| symbol | No | A-share code (000001), HK code (00700), index (sh000001) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions data source (AKShare) but does not disclose behavioral traits like rate limits, data freshness, whether it is read-only, or if authentication is needed. For a data retrieval tool, stating read-only nature would be helpful.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence of 16 words, listing the core functionalities without any fluff. It is front-loaded and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having 6 parameters and no output schema, the description is very brief. It does not explain how parameters relate to actions (e.g., symbol required for ohlcv) or how to format symbol codes. The description is incomplete for making effective use of all tool capabilities.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 83%, so most parameters are already described in the schema. The description adds high-level context but does not provide additional meaning beyond what the schema offers. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it provides A-share and HK stock data, listing specific data types (OHLCV history, current price, symbol search, index daily data). The name and description distinguish it from sibling tools focused on other asset classes like crypto or global assets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description does not provide any guidance on when to use this tool versus alternatives. It lacks explicit context about when this tool is appropriate, prerequisites, or exclusions. The many sibling tools make such guidance valuable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools overlap in providing crypto price data (crypto_price, crypto_market, crypto_derivatives, global_assets) and news (news_feed, tradfi_news). While descriptions clarify some differences, agents may struggle to choose between similar tools.
Tool names mix styles: some are simple nouns (backtest, cn_market), others compound nouns with underscores (crypto_derivatives, derivatives_sentiment). No consistent verb_noun pattern, making it harder to infer purpose from name alone.
With 19 tools covering a broad domain (crypto, DeFi, macro), the count feels slightly high but justifiable. However, several tools could be merged to reduce overlap and improve navigability.
The tool set covers a wide range of market intelligence needs: price data, technical analysis, sentiment, macro indicators, news, and DeFi. Minor gaps like on-chain analytics or direct trading are acceptable given the intelligence focus.