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_promotion

晋级 / 断板追踪: every stock that closed sealed at the limit on the previous trading day, and what it did on trade_date — grouped by yesterday's height (highest first). Each level: count / promoted (sealed again, today_height = height+1) / broken (touched but unsealed) / failed (never reached the limit) / promotion_rate / avg_pct_change (that cohort's premium today). members[] carry canonical_code, name, prev_height, outcome, today_height, pct_change. The core sentiment-cycle read (昨日 3 板今天几家晋级、几家炸、几家跌停) that max_height cannot give. Intraday the outcome is live and can still change before the close.

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

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 today / latest
_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 are supplied, so the description carries the full burden, and it does disclose a genuinely behavioral trait: intraday the outcome is live and can still change before the close, which affects how the agent should present results. It also defines what each outcome bucket means (promoted/broken/failed), removing ambiguity about the data's semantics. It does not address availability of the previous trading day, error behavior, or the response-size conventions, though the schema's _max_bytes params hint at those.

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 front-loaded with the purpose and grouping, then gives the cohort metrics and member fields. The field enumeration is dense but justified because there is no output schema, so the prose is the only place the agent can learn about the return shape. Only minor tightening would be possible.

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 and no annotations, the description supplies both the semantic meaning of each aggregate (`promotion_rate`, `avg_pct_change` as that cohort's premium today) and the member fields, which is the right amount of detail for this complexity. The gaps are around data availability and default date behavior, which are partly covered by the schema.

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 each of the 8 parameters, including the two enums (`include`, `_max_bytes_mode`), is already documented in the schema. The description only implicitly references `trade_date` ('what it did on `trade_date`') and adds no semantics about the include=active/all filter. Baseline 3 applies when the schema already does the work.

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 opens with a specific verb and resource pair (晋级 / 断板追踪) and defines both the population (every stock that closed sealed at the limit on the previous trading day) and the grouping (by yesterday's height, highest first). It explicitly contrasts itself with `max_height`, which cannot give this per-cohort breakdown, so an agent can distinguish it without reading the 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?

It frames the tool around a concrete question ('the core sentiment-cycle read: 昨日 3 板今天几家晋级、几家炸、几家跌停'), which tells the agent when this is the right call, and it names one alternative that cannot answer it. It does not state exclusions or how it differs from the other limit-up siblings such as limit_up_pool or limit_up_history.

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