Skip to main content
Glama

China Stocks

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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

Input Schema

TableJSON 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 / examples
      Previous value: -[
-  {
-    "date": "20240115"
-  },
-  {
-    "date": "2024-01-15",
-    "limit": 10
-  }
-]New value: +[
+  {},
+  {
+    "limit": 10
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "date": "20240115"
+  },
+  {
+    "date": "2024-01-15",
+    "limit": 10
+  }
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context: the data source (Eastmoney, keyless access) and the exact fields returned. It also clarifies the price limit rules. No contradictions with annotations. This exceeds the baseline for annotation-covered tools.

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 a single well-organized paragraph that front-loads the main function, then elaborates on fields and source. It avoids fluff and each sentence contributes useful information. Slightly dense due to the field list, but efficient and readable.

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?

With no output schema, the description thoroughly explains what the tool returns, listing all stock attributes. It also explains the limit percentage rules and source. The parameters and defaults are well-covered by the schema, so the description complements the structured data completely.

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?

The input schema provides 100% coverage for both parameters (date and limit), including defaults and ranges. The description adds no additional parameter semantics beyond what the schema already documents, such as the total count always being returned. Baseline 3 is appropriate because the schema does the heavy lifting.

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 clearly states the tool's purpose: to provide the A-share limit-up board for a trading day, including the count and ranked list of stocks. It specifies the scope (+10%/+20% limits) and distincts from sibling A-share tools (e.g., quotes, consensus) by focusing on limit-up events. The verb 'answers' and example queries make the purpose concrete.

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 context for use, such as answering specific questions like 'how many A-shares hit limit up today' and 'top limit-up stocks'. It implies when to use this tool over alternatives (e.g., when limit-up data is needed), but does not explicitly exclude alternatives or mention when not to use it. This aligns with 'clear context, no exclusions'.

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

All China Stocks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources