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_summary

Limit-up summary for a trade date: limit_up_count / broken_count + ever_broken_count / limit_down_count / max_height / ladder[{height, count}]. Two seal-break measures: broken_count = INSTANTANEOUS boards open right now (day high touched the limit, currently unsealed; auction touches included); ever_broken_count = CUMULATIVE 当日曾炸板家数 (sealed ≥9:30 then broke for ≥30 consecutive seconds, re-sealed included). ⚠️ Different populations, NOT nested — ever_broken_count can be lower than broken_count; never subtract them. '现在多少没封住' → broken_count; '今天封过又开过' → ever_broken_count. ⚠️ Our own measure, not comparable with terminals, and not across 2026-08-25 (rule change). 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_summary"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 substantial work: it discloses that the two seal-break measures are non-nested, non-comparable with terminal data, broken by a rule change on 2026-08-25, and that a pre-open fallback applies. It stops short of explaining what that fallback actually returns, or any latency, permission, or pagination 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?

Front-loaded with the returned field list, then caveats, then a routing shortcut – a sensible order. Dense but nearly every clause carries information; the mixed English/Chinese jargon and the ⚠️ markers are compact rather than wasteful, though a reader must decode terms like 当日曾炸板家数 and '口径'.

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, describing the return fields was mandatory and is done well, including the ladder[{height, count}] shape. The main gaps are the undefined 'Pre-open fallback' behavior and the absence of any hint about which of the several limit_up_* siblings to reach for, which matters given how many exist.

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 per the baseline the schema already documents all eight parameters, including include (active/all 口径) and trade_date. The description adds no parameter-level meaning at all – notably it never explains the active vs all caliber choice, which is the one parameter with real analytical consequence; its detail lands on returned metrics rather than inputs.

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?

The first clause names a specific resource and scope: 'Limit-up summary for a trade date', and then enumerates the exact fields returned (limit_up_count, broken_count, ever_broken_count, limit_down_count, max_height, ladder). An agent knows precisely what the tool produces, but the description never distinguishes it from near-name siblings like limit_up_analysis, limit_up_pool, limit_up_history, or limit_up_promotion.

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 quoted-phrase routing ('现在多少没封住' → broken_count; '今天封过又开过' → ever_broken_count) is genuinely useful disambiguation, but it chooses between two output metrics of the same tool, not between this tool and its siblings. There is no statement of when to prefer limit_up_analysis or limit_up_pool, and no explicit when-not-to-use case beyond the 2026-08-25 comparability break.

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