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_history

Daily limit-up trend over the last N trading days: { trade_date, limit_up_count, broken_count, ever_broken_count, max_height }, oldest first. Same two seal-break measures as limit_up_summary (instantaneous end-of-day vs cumulative ≥30s breaks) — different populations, NOT nested; never subtract the series. ⚠️ The counting rule changed twice: values before mid-June 2026 include auction noise and days before 2026-08-25 count brief flicker — expect a STEP DOWN at 2026-08-25; segments are not comparable.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoLookback window in trading days (1-250, default 30)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it discloses non-obvious data-quality behavior beyond any structured field: counting rules changed twice, pre-mid-June-2026 values include auction noise, pre-2026-08-25 values count brief flicker, and a step down is expected at that date. It does not discuss response-size behavior, but the _spill/_max_bytes parameters already encode that in the schema.

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 record shape and window, then the sibling distinction, then the comparability warning — a sensible information hierarchy. The parenthetical explaining the two seal-break measures is dense but earns its place as it prevents a real misinterpretation; nothing here is padding.

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 correctly compensates by enumerating the returned fields and their order, and it flags the historical discontinuity that would otherwise corrupt trend analysis. For a single-window read tool with fully documented parameters, only a brief note on response-size/truncation behavior is arguably missing.

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 defines days, _jq, _spill, _fields, _intent, _max_bytes and _max_bytes_mode. The description only echoes the 'last N trading days' window and adds ordering ('oldest first'), which is output rather than parameter semantics, so 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+resource+shape: 'Daily limit-up trend over the last N trading days' and enumerates the exact returned fields { trade_date, limit_up_count, broken_count, ever_broken_count, max_height } with ordering ('oldest first'). It also names the sibling limit_up_summary and declares the populations are different, so an agent can distinguish the two without opening either 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?

Gives explicit negative guidance relative to the sibling: 'different populations, NOT nested; never subtract the series', which prevents a concrete misuse. It stops short of a positive routing rule ('use this instead of limit_up_summary when you need a multi-day series'), so usage is strongly implied rather than fully spelled out.

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