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_show

Daily margin-trading (融资融券) series for one A-share: financing balance / gross buy / repayment / net buy, short-sell and short balance (shares and CNY), total balance, day-over-day change. T+1 — the latest row is normally the previous trading day (in backtests visible_date = trade_date + 1). ⚠️ financing_buy_cny is GROSS (includes round-trips) — judge direction by financing_net_buy_cny only; short side likewise by the change in short_balance_shares. ⚠️ null = not published / not derivable (Shenzhen and Beijing publish no repayment), not zero. ⚠️ financing_balance_chg_* is versus prev_trade_date — check it is adjacent.

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

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.1/5.0
Behavior5/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 so well: it discloses T+1 publication lag (with the backtest visible_date rule), that financing_buy_cny is gross and direction must be judged from financing_net_buy_cny, that null means unpublished/underivable rather than zero (Shenzhen/Beijing have no repayment), and that change fields are versus prev_trade_date and adjacency must be checked. These are real behavioral traps an agent would otherwise fall into.

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?

Scope comes first, then the T+1 caveat, then three dense ⚠️ lines each carrying a distinct failure mode. No filler; the bolded clauses and warning markers are functional signposts rather than decoration.

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 10-parameter, output-schema-less tool, the description effectively documents the return payload by enumerating every metric and its interpretation. Pagination/spill behavior is left to the schema's _spill/_max_bytes/_fields descriptions, which is acceptable since those fields are self-documented.

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 schema already documents code, from/to, days and the _-prefixed controls, setting a baseline of 3. The description adds meaning the schema cannot: the code parameter implicitly targets a single A-share and the T+1 behavior frames what from/to and days actually yield, plus the prev_trade_date basis for change fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and unit of analysis ('Daily margin-trading series for one A-share') and enumerates the returned metrics (financing balance, gross buy, repayment, net buy, short-sell, short balance, total balance, change). The per-stock scope implicitly separates it from market-wide siblings like margin_market, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the per-A-share scope and the T+1 note tells the agent what to expect from the latest row, but there is no explicit 'use this instead of margin_market/margin_movers' routing or when-not guidance. The interpretation rules are conditional guidance rather than selection guidance.

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