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_collateral_movers

Ranks A-shares by collateral-eligible holdings (担保券) for one trading day (default latest). Default pct_desc = collateral_pct_of_total_mv (collateral value as % of total cap, percentage points) — how much of a name sits in margin accounts and is exposed to forced liquidation. Other keys: pct_asc, shares_chg_desc / shares_chg_asc, mv_desc. Rows with an unpublished ranking field are excluded, not zero. T+1, published later than margin data — may lag margin_movers by a day. ⚠️ Noisy on small caps — check collateral_mv_cny. Coverage is wider than the margin list.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
sortNoRanking key: pct_desc (default) / pct_asc / shares_chg_desc / shares_chg_asc / mv_desc
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 substantial work: it discloses that rows with an unpublished ranking field are excluded rather than zeroed, that the dataset is T+1 and publishes later than margin data, and that small caps are noisy. It does not describe the returned row shape or pagination, which leaves some behavioral ground uncovered for a 9-parameter tool.

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 scope statement is front-loaded and the caveats follow in a logical order: sorting semantics, exclusion rule, publication lag, then the small-cap warning. It is dense and jargon-heavy with emoji markers, but nearly every clause carries decision-relevant information.

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 tool with no annotations and no output schema, the definition covers the essentials: what is ranked, the default day, every sort key, the null-handling rule, and the freshness caveat. It references a returned field (`collateral_mv_cny`) without enumerating the rest of the row shape, which is the main remaining gap.

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, but the description goes further by defining what the default `pct_desc` actually measures — collateral value as a percentage of total market cap, interpreted as exposure to forced liquidation. That interpretive gloss on the ranking key is meaning the enum alone does not convey; the utility parameters (_jq, _spill, _fields) remain schema-only.

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 collateral-eligible holdings (担保券) for one trading day') and explicitly contrasts its coverage and latency against the sibling `margin_movers`. An agent can distinguish it from margin_movers and margin_collateral without opening any 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 clear operating context: default trade_date is the latest available day, default sort is pct_desc, and alternative sort keys are enumerated with their meanings. It also warns to check `collateral_mv_cny` when small caps look noisy and notes it may lag `margin_movers` by a day, but it never states an explicit when-to-use vs when-to-use-the-other rule.

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