AgentLadle MCP AKShare

get_hot_rank

Read-onlyIdempotent

Retrieve hot stock rankings across CN, HK, and US markets. Use market, rank type, and count parameters to get trending stocks.

Instructions

Get hot stock ranking (热度榜).

Use to find trending stocks. get_hot_rank(market="CN", count=10)

Args: market: CN/HK/US (default CN) rank_type: hot/search (default hot) count: Number of stocks (default 20)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hot_rank"
  }
}

Input Schema

Name	Required	Default
`count`	No
`market`	No	CN
`rank_type`	No	hot

Output Schema

Name	Required	Description	Default
`data`	No
`hint`	No
`error`	No
`cached`	No
`source`	No
`status`	Yes
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate readOnly, openWorld, and idempotent. The description adds parameter details but does not disclose data freshness, rate limits, or the meaning of 'search' vs 'hot'. It adds some value but not extensive beyond annotations.

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 concise with a clear heading, strategy, example, and parameter list. The use of XML tags adds structure, though it is non-standard. No wasted sentences.

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 three optional parameters and an output schema. The description covers the core purpose and parameter choices but omits details on the two rank_type options and does not explain the return format (though output schema exists). It is adequate but not thorough.

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 has 0% description coverage, so the description carries the burden. It lists possible values for market and rank_type, but does not explain the semantics of 'hot' vs 'search' or validate the formats. Partially compensates but incomplete.

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 it gets a hot stock ranking and strategy says 'Use to find trending stocks'. However, it only mentions 'hot' while the tool also supports a 'search' rank_type, which is not explained, causing slight ambiguity.

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 strategy tag provides a clear usage hint ('find trending stocks'), but there is no guidance on when to use this tool versus alternatives (e.g., get_industry_rank or get_limit_up_pool) or when not to use it.

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

Deploy Server