Skip to main content
Glama
Sign In
a-share-mcp

a-share-mcp

by shouldnotappearcalm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_limit_up_pool

Fetch a daily limit-up stock pool with code, name, change, price, seal funds, consecutive boards, first seal time, and industry; optionally filter by date and return top N in markdown, JSON, or CSV.

Instructions

    Fetches limit up stocks pool (涨停股池).
    
    Returns detailed list of stocks hitting daily upper price limit.
    Data source: Eastmoney via Akshare.

    Args:
        date: Date in format 'YYYYMMDD'. Defaults to today.
        top_n: Number of stocks to return. Defaults to 30.
        format: Output format: 'markdown' | 'json' | 'csv'. Defaults to 'markdown'.

    Returns:
        Limit up stocks with: 代码, 名称, 涨跌幅, 最新价, 封板资金, 连板数, 首次封板时间, 所属行业

Input Schema

NameRequiredDescriptionDefault
dateNo
top_nNo
formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the data source ('Eastmoney via Akshare') and the exact fields returned, which is meaningful context for a read-only data tool. It omits behavioral caveats such as what happens when the date is a non-trading day, whether today's data is intraday-partial, or any rate-limiting/availability behavior.

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 Args/Returns structure is front-loaded and easy to scan, with no wasted prose. The opening two sentences are mildly redundant (the pool is restated as 'detailed list of stocks hitting daily upper price limit'), but the cost is small.

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

Completeness4/5

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

No output schema exists, and the description compensates by enumerating the returned columns, so an agent knows the response shape. Combined with full parameter documentation, the definition is close to complete for a simple read-only data fetch; only edge-case behavior around non-trading dates is unaddressed.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it documents all three parameters with format syntax ('YYYYMMDD'), defaults (today, 30, 'markdown'), and the allowed format values ('markdown' | 'json' | 'csv'). The 'today' fallback for date is left slightly ambiguous but otherwise all parameters are covered.

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?

States a specific verb and resource ('Fetches limit up stocks pool') and clarifies with the Chinese term 涨停股池 plus 'stocks hitting daily upper price limit', so the domain concept is unambiguous. It does not explicitly contrast itself with near-neighbors like get_limit_down_pool, get_consecutive_limit_up, or get_limit_up_down, so it stops short of 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?

There is no when-to-use guidance and no exclusions. The sibling list contains several overlapping tools (get_limit_down_pool, get_limit_up_down, get_consecutive_limit_up, get_market_pool_details) and the description gives the agent nothing to decide between them.

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