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

margin_movers

Ranks A-shares by margin-trading activity for one trading day (default latest). Sort: net_buy_desc (default) / net_buy_asc / balance_desc / balance_chg_pct_desc / balance_chg_pct_asc. Ranking by gross buy is deliberately not offered (it would surface net-outflow names as leveraged buying). T+1 — the ranked day is normally the previous trading day. balance_chg_pct_* is noisy on small balances — check financing_balance_cny.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
sortNoRanking key: net_buy_desc (default) / net_buy_asc / balance_desc / balance_chg_pct_desc / balance_chg_pct_asc
limitNoNumber of rows to return (1-200, default 30)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
trade_dateNoYYYY-MM-DD. Defaults to the latest trading day present in the data.
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 real work: it discloses the T+1 lag ('the ranked day is normally the previous trading day'), the default day behavior, the intentional omission of a gross-buy sort with reasoning, and a data-quality warning about noisy percentage changes. It does not cover auth, rate limits, or response shape, which keeps it from a 5.

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

Conciseness5/5

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

Every sentence is load-bearing: scope first, then sort options, then the rationale for the omission, then the T+1 caveat, then the noise warning. Dense but front-loaded and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, annotation-free tool with no output schema, the description covers domain behavior well but never describes the returned rows beyond a passing field mention, and the framework parameters (_jq, _spill, _fields, _max_bytes) rely entirely on schema text. Adequate for correct invocation, but not fully self-contained on result shape.

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 the baseline is 3; the description exceeds it by explaining the meaning of each sort enum value and the rationale for excluded options, plus a caution tying `balance_chg_pct_*` to `financing_balance_cny`. The `trade_date` default and `limit` are already documented in the schema, so those add nothing new.

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-shares by margin-trading activity for one trading day' — with a scope (single trading day, default latest) that cleanly separates it from collateral- or market-movers siblings. An agent can tell what it returns without opening 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?

Gives concrete selection guidance: which sort keys exist, why gross-buy ranking is deliberately absent, and a caveat steering the agent to check `financing_balance_cny` when using `balance_chg_pct_*` on small balances. It stops short of naming a sibling tool to use for a different question, but the when/how guidance for its own parameters is solid.

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