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_seats

Ranks brokerage branch seats (营业部) by dragon-tiger activity: appearances, cumulative buying, and how their picks opened the NEXT session. Counting is deduplicated by (day, exchange, security, seat). ⚠️ Read win_rate_pct with win_samples — small samples are noise (min_appearances gates win-rate sorting). ⚠️ 机构专用 and 沪/深股通专用 are shared placeholder names, not individual seats — excluded by default; request them explicitly and check is_aggregate. No per-seat NET figures (Shanghai discloses one side per seat).

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
sortNoRanking key (default appearances_desc).
limitNoSeats to return (1-200, default 50).
_spillNotrue=全量落盘,只回摘要与取数地址
windowNoLook-back window (default 30d).
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
seat_typeNoRestrict to one seat kind. Omit for branches only — the meaningful leaderboard.
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀
min_appearancesNoMinimum appearances to qualify (default 3). Also gates win-rate sample count when sorting by win rate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose real behavior: deduplication by (day, exchange, security, seat), default exclusion of 机构专用/沪股通专用 placeholders, and the data limitation that Shanghai discloses only one side per seat (no net figures). It does not cover cost, rate limits, or response shape, which is a meaningful gap for an unaided 11-parameter tool.

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?

Front-loads what is ranked and how counting works, then uses two ⚠️-marked caveats for the traps an agent is most likely to fall into. Every sentence carries information; nothing is restated from the title or schema.

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 an 11-parameter, no-output-schema, no-annotation tool, it covers the semantically risky parameters and names result fields the agent will encounter (win_rate_pct, win_samples, is_aggregate). The remaining gap is that the actual response structure and sort-key behavior are not sketched, though the schema covers parameter-level defaults.

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 baseline is 3; the description goes beyond it by explaining the coupling between min_appearances and win-rate sorting, and by clarifying that omitting seat_type yields branches only rather than all seat kinds. That is genuine semantic value the schema alone does not convey.

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?

States a specific verb and resource — "Ranks brokerage branch seats (营业部) by dragon-tiger activity" — and enumerates the metrics ranked (appearances, cumulative buying, next-session open of picks). It implicitly separates itself from daily/stock siblings by scoping to seat-level leaderboards, but never names an alternative tool explicitly.

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?

Gives concrete conditional guidance: read win_rate_pct only alongside win_samples, use min_appearances to gate win-rate sorting, and request aggregate placeholders explicitly rather than by default. It stops short of routing the agent to a sibling when a single-seat lookup or a per-day view is actually needed.

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