Skip to main content
Glama
This connector has been deprecated

Replaced by echopai-mcp.

Duplicate listing; superseded by io.github.echopai/echopai-mcp (official MCP Registry entry).

limit_up_pool

A-share limit-up pool for a trade date, per stock: first/last seal time, final pct, seal amount (CNY) / volume (lots), max_seal_amount + max_seal_time (the day's peak seal), broken_count, consecutive_days (连板数), board_count_within, one-word-board flag, status (limit_up / broken), board class. Read max_seal_amount / seal_amount: peak >> current = 封单被吃掉, ≈ 1 = 封单从来就薄. ⚠️ The peak has no history before 2026-08-25 (0 / null = not recorded — never substitute seal_amount). broken_count = 当日开板次数, debounced: counts breaks below the limit lasting ≥30 consecutive seconds after a genuine intraday seal (auction touches never count); kept after re-sealing. ⚠️ Our own measure — not comparable with terminals' 开板次数, not with the broken_count of limit_up_summary, and not across 2026-08-25 (older dates used a per-snapshot rule). 行内提供 pct_change(兼容 final_pct)、turnover_rate、amount、main_net_in、super_net_in,资金流为当日最新已存分钟累计元;metrics_trade_date、quote_as_of、fundflow_as_of 标明日期和源时间,缺测为 null,历史不混入今日数据。 Rows include same-day reason / concept_tags / attributed_at, preferring LLM leading_concept while keeping graph_leading_concept; attribution outages are explicit. prev_trade_date and nullable resumed_after_suspension distinguish recorded suspensions from data gaps. Sort: consecutive_days → board_count_within → seal_amount, desc. Pre-open fallback applies.

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": "limit_up_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
includeNoactive = 排除 ST/退市(默认); all = 全部active
_max_bytesNo响应字节上限,默认约 50 KB
trade_dateNoISO date YYYY-MM-DD; omit for latest (pre-open fallback)
include_brokenNotrue 时连炸板(status=broken)也一起返回;默认只返回当前封板 status=limit_up
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so unusually well: it discloses the peak-seal data gap before 2026-08-25 and forbids substituting seal_amount, explains the 30-second debounce rule for broken_count, flags incomparability with terminal data and across the date boundary, and states that missing measurements are null and outages are explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the subject and then sprawls into a dense serialized data dictionary mixing English, Chinese terms, and warning glyphs. Most content earns its place, but the field enumeration could be tightened without losing information.

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?

There is no output schema, so the description must describe the returned rows, and it does so thoroughly — measures, attribution fields, as-of markers, nullable flags, and sort order. Residual gap is that no explicit usage routing or data-freshness cadence is stated.

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 the schema already documents trade_date, include, include_broken, and the _-prefixed controls. The description only marginally adds meaning (pre-open fallback for trade_date, semantics of resumed_after_suspension), so it sits at the baseline.

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 the resource (A-share limit-up pool) and the granularity (per stock for a trade date), then enumerates the returned measures. It distinguishes itself from limit_up_summary by explicitly warning that its broken_count is not comparable with that sibling's — a concrete differentiator an agent can act on.

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?

Implied usage is clear from the content, and the include_broken default and pre-open fallback are noted, but there is no explicit 'use this when' / 'use X instead' routing beyond the broken_count caveat. An agent knows what it gets but must infer which sibling to pick.

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.

Resources