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_seat

One seat deduplicated dragon-tiger appearance history: which names it traded, on which side, for how much, and how each opened the next session. Deduplication and side semantics match dragon_tiger_seats — one row per (trading day, security, side), amounts are the seat OWN side only, and null means the exchange did not disclose that side rather than zero. Use it to check whether a name on today board is a seat regular before reading anything into a single appearance.

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": {
      "name": "<name>"
    },
    "name": "dragon_tiger_seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
nameYesSeat name exactly as disclosed, e.g. 东方财富证券股份有限公司拉萨金融城南环路证券营业部
limitNoRows to return (1-200, default 50).
_spillNotrue=全量落盘,只回摘要与取数地址
windowNoLook-back window (default 30d).
_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
Behavior4/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 well: it discloses the dedup key (one row per trading day, security, side), that amounts are the seat's OWN side only, and that `null` means non-disclosure rather than zero. It omits anything about pagination limits or response volume beyond what the schema's `limit`/`_max_bytes` fields already declare.

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?

Three dense sentences with zero padding: what it returns, how its semantics align with the sibling, then the recommended use. Semantics are front-loaded ahead of the usage advice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, schema-fully-documented read tool with no annotations and no output schema, the description supplies the missing pieces an agent needs: row grain, side/amount semantics, null meaning, and a concrete decision scenario. Nothing material is left ambiguous for correct invocation.

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 coverage is 100%, so the baseline is 3. The description reinforces that `name` means one exact seat and clarifies the meaning of `null` values in results, but adds no syntax or format guidance for `window`, `limit`, or the underscore-prefixed control parameters.

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 resource and scope: a single seat's deduplicated dragon-tiger appearance history, covering names, side, amount and next-session open. It explicitly anchors its semantics to the sibling `dragon_tiger_seats`, so an agent can tell this per-seat lookup apart from the multi-seat list without opening either schema.

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?

Provides a concrete use case: check whether a name on today's board is a seat regular before reading anything into a single appearance. It also routes to `dragon_tiger_seats` for the shared dedup/side semantics, but does not state when NOT to use this tool or name any other alternative.

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