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

trades_ticks

⚠️ EXPERIMENTAL — may change or be withdrawn at any time. Do not build automation on it or persist it as a system of record. Individual prints for one A-share on one trading day, in seq order with cursor paging — for inspecting a specific moment; for whole-session work use trades_minute. ⚠️ Not exchange tick data: one row is everything traded in a 3-second window, so to find large trades filter on min_amount — counting rows will not do it. ⚠️ side is inferred from bid/ask (M = neither). ⚠️ seq may have gaps (backfilled after the close). ⚠️ No 09:25 auction print — never take an open price here. Page with after_seq = previous next_after_seq until null (a day is ≤3 pages at the default limit). Retention 60 trading days (retention_from); coverage starts 2026-06-01.

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

Input Schema

NameRequiredDescriptionDefault
toNoLatest print time HH:MM (China time), inclusive.
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesCanonical code of one A-share security (e.g. SSE:600519)
dateNoTrading day YYYY-MM-DD (China time). Omit for the latest day that has data.
fromNoEarliest print time HH:MM (China time), inclusive.
sideNoB = buyer-initiated, S = seller-initiated, M = neither. Inferred from the book.
limitNoRows per page (1-2000, default 500).
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
after_seqNoCursor: only prints with seq greater than this. Use the previous next_after_seq.
_max_bytesNo响应字节上限,默认约 50 KB
min_amountNoKeep only prints reaching this turnover in yuan — the way to find large trades.
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and discloses the key behavioral traits: experimental status, 3-second aggregation rather than exchange ticks, inferred side, seq gaps, missing 09:25 auction print, retention window, and coverage start date.

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?

The description is dense but front-loaded with the experimental warning and the trades_minute alternative. Every sentence carries either a caveat or an operational instruction, with no filler.

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?

Given 14 parameters and no output schema, the description covers the major invocation rules, paging protocol, data caveats, and retention. It does not detail returned columns or auth/rate limits, which is a minor remaining gap rather than a blocker.

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 still adds practical meaning beyond the schema for min_amount, side inference, and after_seq cursor usage, though it does not add meaning for every parameter.

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: individual prints for one A-share on one trading day, in seq order with cursor paging. It also explicitly distinguishes itself from trades_minute for whole-session work, so an agent can select it 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use this for inspecting a specific moment and directs whole-session work to trades_minute. It also gives concrete operational guidance: page with after_seq until next_after_seq is null and filter on min_amount to find large trades.

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