Skip to main content
Glama

Ashares Limit Up

ashares_limit_up
Read-onlyIdempotent

The Chinese A-share market's LIMIT-UP board (涨停板) for a trading day, how many stocks hit their daily price limit (+10%, or +20% for STAR/ChiNext) and the ranked list of those stocks. Answers 'how many A-shares hit limit up today', 'top limit-up stocks', 'which stocks 涨停'. Each stock includes code, name, price, change %, turnover (成交额), float market cap, turnover rate (换手率), consecutive-board count (连板数 lbc), first/last seal time, seal fund (封板资金), and industry (行业). Source: Eastmoney (keyless).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
dateNoTrading day as YYYYMMDD or YYYY-MM-DD (default: most recent trading day).
limitNoHow many stocks to return, 1-100 (default 30). The total count is always returned regardless.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many stocks to return, 1–100 (default 30). The total count is always returned regardless."New value: +"How many stocks to return, 1-100 (default 30). The total count is always returned regardless."
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "date": "20240115"
      -  },
      -  {
      -    "date": "2024-01-15",
      -    "limit": 10
      -  }
      -]New value: +[
      +  {},
      +  {
      +    "limit": 10
      +  }
      +]
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "date": "20240115"
      +  },
      +  {
      +    "date": "2024-01-15",
      +    "limit": 10
      +  }
      +]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (Eastmoney, keyless) and the full field set returned per stock, including domain-specific fields like lbc and seal fund.

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?

Front-loaded with the core purpose, then the example queries, then the field list and source. Dense but every clause carries information; the field enumeration is long but justified given there is no output schema.

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?

With no output schema, the description compensates by listing the returned fields, and it discloses the data source and default behavior. Complete enough to call correctly; only the absence of explicit sibling routing keeps it from a 5.

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 coverage is 100%, so both parameters (date format, limit range) are already fully documented in the schema. The description adds only the note that the total count is always returned regardless of limit, which is a minor clarification rather than new parameter meaning. Baseline 3 applies.

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?

States a specific verb and resource ('LIMIT-UP board for a trading day'), gives the exact threshold semantics (+10%, +20% for STAR/ChiNext), and enumerates the concrete questions it answers. An agent can distinguish it from a limit-down or general market-snapshot tool without opening the schema.

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 example questions ('how many A-shares hit limit up today', 'top limit-up stocks') imply when the tool applies, but there is no explicit when-not guidance or named alternative such as ashares_limit_down. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.