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_minute

Who is actually buying — from the trades themselves. Per-minute (or 5/15/30/60-minute) aggregates over the raw trade feed for one A-share: buyer- vs seller-initiated volume, large-print counts, true VWAP. The self-verifiable counterpart to fundflow (the vendor's own classification) — the two routinely disagree. buy_ratio = buy_vol / (buy_vol + sell_vol); ⚠️ Neutral volume is deliberately excluded from the denominator. vwap is yuan per share. ⚠️ big_count / big_amount use a fixed 200,000-yuan-per-print line, meaningless on high-priced names (贵州茅台: 97 of 99 prints in one 5-minute bucket cleared it) — compare a stock with itself only; unrelated to fundflow tiers. ⚠️ tick_count counts the prints we captured (3-second snapshots), not the exchange's trade count. Omit date for the latest day that has data. History starts 2026-05-26; earlier = not covered.

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

Input Schema

NameRequiredDescriptionDefault
_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.
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
intervalNoBucket size in minutes: 1 / 5 / 15 / 30 / 60 (default 5).
_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?

No annotations are supplied, so the description carries the full burden, and it does: it discloses the neutral-volume exclusion from the buy_ratio denominator, units (yuan per share), the fixed 200,000-yuan large-print threshold and why it breaks on high-priced names, and that `tick_count` reflects 3-second captured snapshots rather than exchange trade counts. These are exactly the non-obvious traits an agent could otherwise misreport.

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 with the one-line purpose, then field definitions, then warnings, so scanning is easy. It is dense with caveats but each warning maps to a real misreading risk; only minor redundancy (interval list also in schema) could be trimmed.

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 9-parameter tool with no output schema and no annotations, the description compensates well by defining the returned fields (buy_ratio, vwap, big_count, big_amount, tick_count) and the data-coverage window. It says little about the envelope/wrapper parameters (_jq, _spill, _max_bytes) and response size behavior, which are left entirely to the schema.

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%, and the schema already documents the interval options, the default of 5, and the 'omit date for latest' rule. The description restates the interval choices and date behavior without adding format or edge-case detail beyond the schema, so the baseline of 3 applies.

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 and resource: per-minute aggregates (1/5/15/30/60) over the raw trade feed for a single A-share, yielding buyer- vs seller-initiated volume, large-print counts and true VWAP. It explicitly positions itself against the sibling `fundflow` (vendor classification vs. self-computed), so an agent can choose between them 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?

Gives clear usage context: it is the self-verifiable counterpart to `fundflow`, and the two 'routinely disagree', which tells the agent when to prefer it. It also states the `date` omission behavior and the 2026-05-26 history floor, which prevents futile queries. It stops short of explicit when-not guidance (e.g. preferring `trades_ticks` for individual prints).

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