AgentLadle MCP AKShare

get_limit_up_pool

Read-onlyIdempotent

Retrieve the limit-up stock pool (涨停) for a given date. Defaults to today if no date specified.

Instructions

Get limit-up stock pool (涨停板).

Leave date empty for today; specify for historical. get_limit_up_pool(date="2026-07-08")

Args: date: Date YYYY-MM-DD (default: today)

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_limit_up_pool"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No

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

A4.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety. The description adds minimal behavioral context (date default behavior) but is not contradictory.

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 concise: purpose, strategy, example, arguments. Every sentence adds value and is front-loaded.

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

Completeness5/5

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

For a simple tool with one optional parameter and an output schema present, the description covers all necessary usage aspects: purpose, parameter, and example.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema lacks parameter descriptions (0% coverage). The description compensates with 'Args: date: Date YYYY-MM-DD (default: today)', specifying format and default behavior clearly.

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 explicitly states 'Get limit-up stock pool (涨停板)', using a specific verb and resource. It is clearly differentiated from sibling tools like get_limit_down_pool.

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?

The description provides clear guidance on when to leave date empty (today) versus specify a date (historical). However, it does not explicitly state when not to use this tool or suggest alternatives among the many sibling tools.

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

Deploy Server