Skip to main content
Glama

Ashares Limit Down

ashares_limit_down
Read-onlyIdempotent

The Chinese A-share market's LIMIT-DOWN board (跌停板) for a trading day, how many stocks hit their daily DOWN price limit (-10%, or -20% for STAR/ChiNext) and the ranked list of those stocks. Answers 'how many A-shares hit limit down today', '跌停家数', 'which stocks 跌停', 'limit-down stock count for a China A-share trading day', the counterpart to ashares_limit_up, together giving market-wide limit-up/limit-down breadth. Each stock includes code, name, price, change % (negative), turnover (成交额), float market cap, turnover rate (换手率), seal fund (封板资金), last seal time, industry (行业), and P/E. 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_down"
  }
}

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. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description adds real context beyond them: the data source is Eastmoney and requires no key, the default is the most recent trading day, the limit caps the returned rows while the total count is always returned, and the threshold semantics (-10%, or -20% for STAR/ChiNext) are spelled out. It does not discuss rate limits or ordering criteria for the 'ranked' list.

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 resource and scope, then the answerable questions, then the returned field enumeration. Dense but every sentence carries information; the field list is long yet serves the missing 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 enumerating returned fields (code, name, price, change %, turnover, float cap, turnover rate, seal fund, last seal time, industry, P/E) and the data source. The main remaining gap is what the 'ranked list' is ranked by, which matters for interpreting results.

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 description coverage is 100%, so both parameters (date format and limit range) are already fully documented in the input schema. The description reinforces the date default and the fact that the total count is returned independently of the limit, but adds no syntax or formatting detail beyond that, so the baseline of 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+resource: the A-share LIMIT-DOWN board for a trading day, returning the count of stocks at the daily down limit plus a ranked list. It explicitly distinguishes itself from the sibling ashares_limit_up as the complementary half of market breadth, so an agent can tell the two apart without opening a schema.

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?

Usage is framed through concrete question patterns ('how many A-shares hit limit down today', '跌停家数', 'which stocks 跌停'), and the sibling ashares_limit_up is named as the counterpart. There is no explicit when-not-to-use or exclusion, which keeps it just short of a 5.

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.