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_market

Market-wide margin-trading (融资融券) series, two arrays. exchanges: per-exchange daily summary (SSE / SZSE / BSE) — balances, gross buy, repayment, net buy, short-sell, derived_fields. structure: market-wide leverage metrics, most importantly avg_maintenance_ratio (margin-call pressure; below 1.3 is the forced-liquidation line), plus balance vs free-float cap, short-sell value, margin share of turnover, account counts and collateral value. T+1, and structure publishes later — the two arrays may not end on the same date; read each row's trade_date. Direction = exchanges[].financing_net_buy_cny; structure[].financing_buy_cny is gross.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoLook-back window in calendar days (1-250, default 60)
_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

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Because the annotations are absent, the description must carry the full burden of disclosure, and it does so better than most: it discloses the T+1 publication lag, warns that `structure` publishes later so the two arrays may not end on the same date, and defines the field meanings needed to avoid misreading the data, including the 1.3 forced-liquidation threshold for `avg_maintenance_ratio`. It never mentions authentication, rate limits, data coverage start dates, or how the response is shaped when `days` exceeds available history, which keeps it short of 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.

Conciseness4/5

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

The description is dense but front-loaded: the tool's identity appears in the first clause, the two arrays are introduced next, and field semantics follow. Every sentence carries information, but the mid-sentence field enumerations and bold markers make it read like documentation rather than guidance, and it takes a second pass to parse which fields belong to which array.

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?

There is no output schema, so the description must explain the return shape, and it does: it names the two arrays, lists key fields in each, and gives interpretation anchors such as the maintenance-ratio threshold and the gross-versus-net distinction. It does not state units consistently across all listed fields or what happens when `_spill` or `_max_bytes` truncation applies, which means a gap remains, but overall it is complete enough for an agent to call the tool and read the data correctly.

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 the schema already documents `days`, `_jq`, `_fields`, `_spill`, `_max_bytes`, `_max_bytes_mode`, and `_intent`. The description adds nothing about parameter behavior: it does not mention that `days` defaults to 60 calendar days, nor how `_jq` interacts with the two-array response. Baseline 3 applies when the schema already does this work.

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?

The description clearly states a specific resource: market-wide margin-trading (融资融券) data returned as two arrays, `exchanges` at the exchange level and `structure` at the market-wide leverage level. The word 'Market-wide' implicitly distinguishes this tool from the sibling tools that cover single-stock or mover-scoped margin data, but the description never names those siblings, so the contrast with them remains implicit rather than explicit.

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?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance, so the agent must infer that this tool is the right choice for aggregate leverage context. The only operational guidance is about interpreting results, such as 'read each row's `trade_date`' and 'Direction = `exchanges[].financing_net_buy_cny`'; this is useful usage guidance in the sense of field handling, but it does not help the agent choose between this tool and its siblings.

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