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

dragon_tiger_stock

One security's dragon-tiger (龙虎榜) appearance history, newest first, each with its full buy/sell seat table — is the money institutional, northbound or retail-branch hot money, and do the same seats keep coming back. Caveats as dragon_tiger_daily: end-of-day data (the newest row is never today's flow); one row per qualifying reason; net_buy_cny covers the top-five disclosed seats only; totals aggregate each side's OWN list, smaller than vendor UNION totals — reconcile on seats[]; Shanghai null = not disclosed, not zero. Empty = not on the list in the visible window (depth follows plan tier). Amounts CNY, ratios percentage points.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesCanonical A-share code (e.g. SZSE:000533)
limitNoNumber of past appearances to return (1-200, default 30).
_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.3/5.0
Behavior5/5

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

Goes well beyond the annotations with substantive behavioral detail: end-of-day data so the newest row is never today's flow, one row per qualifying reason, `net_buy_cny` covering only top-five disclosed seats, totals aggregating each side's own list rather than vendor UNION totals with a reconciliation instruction, Shanghai `null` meaning undisclosed rather than zero, and empty meaning not listed in the visible window. Note the annotations set `readOnlyHint: false` for what the description presents as a pure read query — a tension worth checking, but the description itself makes no write claims, so this is not a direct contradiction.

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?

Dense but front-loaded: the scope ('One security's ... appearance history, newest first, each with its full buy/sell seat table') comes first, followed by the caveats. Every clause carries information, though the run-on caveat block would read better as separated points rather than one long sentence.

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?

With no output schema, the description carries the return-value burden and does explain key returned fields (`seats[]`, `net_buy_cny`), units (CNY, percentage points), ordering, and empty/`null` semantics. It stops short of describing the full row shape (reason labels, date fields, seat-name fields), so an agent still cannot fully predict the payload.

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 description coverage is 100%, so the baseline is 3; the description adds real meaning on top by explaining that `limit` depth is bounded by the visible window and plan tier, so a requested count may not be fully honored. It does not explain the `code` pattern, `_jq`, `_spill`, or `_fields`, but those are already documented in 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?

States a specific verb-resource-scope: one security's dragon-tiger appearance history, newest first, including the full buy/sell seat table. It also frames the analytical question the data answers (institutional vs northbound vs retail-branch hot money, seat persistence), which lets an agent tell it apart from the market-wide sibling `dragon_tiger_daily`.

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 rather than stated: an agent can infer this is the per-stock drill-down, and the caveat 'as `dragon_tiger_daily`' points to a related tool for definitions. But there is no explicit when-to-use/when-not, no statement of how it differs operationally from `dragon_tiger_daily`, `dragon_tiger_seat`, or `dragon_tiger_seats`, and no prerequisites such as plan-tier limits beyond 'depth follows plan tier'.

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