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

market_movers

A-share top-N movers from the live snapshot (or a past trading day via date). Sort keys: pct / pct_asc / speed / amount / turnover / total_mv / main_net_in / main_net_in_asc; rows with a null sort value land last in both directions. Downloads the full ~3 MB snapshot and ranks client-side — scan with sort + limit ranks server-side and is cheaper. Empty with a note during 09:00-09:14. Each row carries industry and top_concept; both are often missing — coverage, not failure (top_concept a subset of A-shares; industry excludes BSE:*), and top_concept is not the limit-up leading_concept, which is not served here. Live rows also expose top_base_concept {id,name,kind:base,pct_change} and top_concept_status / top_base_concept_status (ready, no_membership, no_snapshot, unavailable). The two layers rank independently; use kind=base for base detail. Historical rows carry neither current theme field nor their statuses. The snapshot includes ETFs: pass security_type=stock for a stock-only amount board. Historical date boards sort only by pct / pct_asc / amount / turnover, carry no top_concept, and cannot combine concept_id.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
topNoTop N items (1-500, default 20)
dateNoPast A-share trading day (YYYY-MM-DD) to rank instead of the live snapshot — that day's daily bars. Omit for today. Only pct / pct_asc / amount / turnover sort historically; concept_id cannot be combined.
sortNoSort field: pct / pct_asc / speed / amount / turnover / total_mv / main_net_in (主力净流入榜) / main_net_in_asc (净流出榜)pct
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
includeNoactive = 排除 ST/退市(默认); all = 全集(含 ST + 退市 + 未知 status)active
exchangeNoNarrow to one exchange: SSE / SZSE / BSE
_max_bytesNo响应字节上限,默认约 50 KB
concept_idNoRank inside one concept / industry instead of the whole market. Filtering happens server-side before ranking, so this is the concept's own leaderboard rather than the market top-N intersected with it. An unknown / inactive / wrong-dimension id returns 404. Get ids from `concepts_list` or `concepts_of`.
concept_kindNoDimension of `concept_id`: concept (themes, default) or industry (Shenwan). Ignored alone.
security_typeNostock = 只看股票 / etf = 只看 ETF / all(默认)= 两者都要。成交额榜(sort=amount)不传 stock 会被货币 / 短融 ETF 占住头部。服务端在 top-N 截断前过滤。
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/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 does so well: it discloses the client-side download cost, pre-open empty behavior, null-safe sort ordering (nulls last in both directions), field coverage caveats for `industry`/`top_concept`, and the enumerated status values for theme layers, plus the independent ranking of the two layers.

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 purpose and cost trade-off, and nearly every clause carries operational information. It is a dense single block, though, and the theme-layer paragraph (`top_base_concept`, statuses, kind=base) is packed enough that an agent may need to re-read it.

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?

For a 14-parameter tool with no annotations and no output schema, this covers purpose, cost, edge cases, row contents, and historical limitations well. Remaining gaps are minor: it never sketches the response envelope (items vs. data, how `_spill`/`_jq` interact) beyond naming per-row fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds real meaning on top — null sort-value ordering, historical sort-key restrictions, `concept_id` being server-side filtering before ranking, and the `security_type` caveat for the amount board. It stops short of explaining the underscore-prefixed control params (`_spill`, `_max_bytes_mode`, `_fields`), which the schema handles.

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 and resource: ranks A-share top-N movers from the live snapshot or a past trading day via `date`. It immediately distinguishes itself from the sibling `scan`, which ranks server-side, so an agent can choose between them 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing guidance: `scan` with `sort` + `limit` is cheaper, this tool downloads the full ~3 MB snapshot and ranks client-side. It also names when-not conditions — empty with a `note` during 09:00-09:14, historical dates limited to four sort keys and incompatible with `concept_id`, and `security_type=stock` needed for a stock-only `amount` board.

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