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_daily

Official dragon-tiger list (龙虎榜) for one trading day, ranked by top-five seats' net buying: brokerage branches, institutional seats (机构专用) and northbound desks. Published the evening after the close — during trading hours it returns the PREVIOUS trading day; always state the response's trade_date. Check coverage per exchange (complete / complete_empty / pending / failed) before concluding a name is absent. A name can appear once per qualifying reason (reason_category) — do not dedupe. ⚠️ net_buy_cny nets the top-five DISCLOSED seats only; not comparable with moneyflow. ⚠️ Totals aggregate each side's OWN list, whereas vendors aggregate over the UNION of both lists, so vendor totals run larger — reconcile on seats[], not on totals, and do not report the gap as a data error. ⚠️ Shanghai (incl. STAR) discloses one side per seat: sell_cny = null on a buy-side seat means NOT DISCLOSED, not zero. Prefer the precomputed institution_net_cny / has_northbound. Amounts CNY, ratios percentage points.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
dateNoTrading day YYYY-MM-DD. Omit for the latest day that has data (during trading hours that is the previous trading day).
kindNoSecurity kind; defaults to stock (B shares / funds / convertibles excluded).
sortNoSort key and direction (default net_buy_desc): net_buy / pct_change / amount / buy_total / sell_total / institution_net, each _desc or _asc. Rows with no value for the chosen field always sort LAST, ascending included — an ascending page of nulls would look like the smallest names when it is really just the ones with no data.
limitNoRows to return (1-500, default 200).
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
categoryNoFilter by qualifying reason: deviation_up/deviation_down (daily move deviation), turnover, amplitude, three_day_deviation_up/down (3-day cumulative), consecutive_limit, abnormal_severe, st_risk, new_listing, no_limit, other
inst_onlyNoOnly rows whose BUY side contains an institutional seat (机构专用).
_max_bytesNo响应字节上限,默认约 50 KB
northboundNoOnly rows where a northbound (沪深股通) seat appears on either side.
_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 present, the description carries the full burden and does so thoroughly: publication timing, per-exchange coverage states (complete/complete_empty/pending/failed), the once-per-reason_category non-deduping rule, the fact that net_buy_cny covers only disclosed top-five seats and is not comparable with moneyflow, and the vendor total-reconciliation caveat. It also discloses a genuinely non-obvious data quirk — Shanghai one-sided disclosure where sell_cny = null means NOT DISCLOSED rather than zero.

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?

Front-loaded correctly: the first sentence defines the tool, and all caveats follow in descending order of consequence. It is dense and uses bold/emoji warning markers effectively, but at six-plus clauses it is close to overstuffed — a reader must hold several unrelated caveats simultaneously.

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 13-parameter tool with no output schema, the description covers the key response surfaces an agent needs: `trade_date`, per-exchange `coverage`, `seats[]` as the reconciliation unit, and the precomputed `institution_net_cny` / `has_northbound` fields to prefer. It stops short of describing the overall response envelope or pagination, which is a real gap given no output schema exists.

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 13 parameters are already documented, including the sort null-last rule, limit bounds, and enum meanings. The description adds interpretive value for the domain concepts behind `inst_only` / `northbound` (机构专用 and 沪深股通 desks) and the `reason_category` duplication rule, but adds no syntax or format detail the schema lacks, so the baseline 3 applies.

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 opens with a specific verb+resource: the official dragon-tiger list (龙虎榜) for one trading day, ranked by top-five seats' net buying, and names the seat sources (brokerage branches, 机构专用, northbound). The 'one trading day' framing implicitly separates it from the per-stock and per-seat siblings, but no sibling is named explicitly, so it lands just short of 5.

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 gives clear operational context for when results should be interpreted a certain way — published the evening after close, so intraday calls return the previous trading day, and coverage must be checked before concluding a name is absent. What is missing is explicit routing guidance: it never says to use dragon_tiger_seats or dragon_tiger_stock instead under particular conditions.

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