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

Daily collateral-eligible holdings (担保券) series for one A-share: collateral_shares, collateral_shares_chg, prev_collateral_shares, collateral_mv_cny, total_mv_cny, collateral_pct_of_total_mv (collateral value as % of total cap, percentage points — a high and rising share means more of the float is exposed to forced liquidation). T+1, published later than margin_show (may lag by a day). Coverage is wider than the margin list, so presence here without margin_show is not a gap. null = not published, not zero.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "margin_collateral"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD. Must be given together with `from`.
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesCanonical A-share code (e.g. SSE:600519)
daysNoLook-back window in calendar days (1-250, default 60). Ignored when from/to given.
fromNoStart date YYYY-MM-DD. Must be given together with `to`.
_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.2/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 behavioral burden. It discloses important traits: T+1 latency, possible one-day lag relative to `margin_show`, wider coverage than the margin list, and that `null` means not published rather than zero. It does not cover permissions, rate limits, or response structure, but no output schema exists and the core data semantics are well explained.

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?

The description is a single dense paragraph that front-loads the returned series and field list, then adds interpretation, latency caveat, coverage note, and null semantics. Every sentence earns its place, with no redundant wording.

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?

Given ten parameters (only one required), no output schema, and no annotations, the description does a thorough job explaining the returned fields, their meaning, lag behavior, coverage, and null handling. It stops short of explaining the generic control parameters (`_jq`, `_spill`, `_fields`) or units for every numeric field, but those are covered by the schema and are not central to correct invocation.

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 all parameters are already documented in the schema. The description adds only indirect parameter meaning: 'for one A-share' implies the `code` requirement, and 'series' implies a time range. No additional syntax or constraints are provided beyond the schema.

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 names the specific resource (daily collateral-eligible holdings series for one A-share), enumerates the exact fields returned, and distinguishes itself from sibling `margin_show` by stating it is T+1 and has wider coverage. An agent can tell exactly what this tool provides 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?

It clarifies the relationship to `margin_show`: this series is published later and has wider coverage, so absence from `margin_show` is not a gap. That gives clear context for when this tool is appropriate, but it does not explicitly state when to use an alternative instead.

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