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

etf_flows

Ranks ETFs by estimated net creation/redemption in CNY over a 1/5/20 trading-day window. An estimate (share change × that day's unit NAV), not a reported flow, and null is not 0: uncomputable days (stale shares / NAV, share-conversion dates) are skipped — read valid_days with the total. ⚠️ Without asset_class, money-market ETFs dominate by one to two orders of magnitude; asset_class=equity fixes that but drops every Shanghai-listed fund.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
limitNoMax items (default 50)
_spillNotrue=全量落盘,只回摘要与取数地址
windowNoAccumulation window (default 1d)
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
directionNoin = largest net creation (default), out = largest net redemption
_max_bytesNo响应字节上限,默认约 50 KB
asset_classNoShenzhen-only; use equity to keep money-market funds off the ranking
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and handles it well: it discloses the estimation method (`share change × that day's unit NAV`), that null days are skipped rather than zero, and that `valid_days` must be read alongside the total. It stops short of describing ordering ties, tie-breaking, or response shape beyond `valid_days`.

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 and dense — the purpose and the two big caveats (estimate, null≠0) land in the first two sentences. The bold/emoji markup and parenthetical formula push it toward the edge of readability without containing waste.

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 10-param ranking tool with no output schema and no annotations, the description covers the two things an agent could get wrong — treating the flow as reported and treating null as zero — plus the money-market distortion. Nothing essential to a correct call is missing.

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, but the description genuinely adds meaning: `asset_class` is Shenzhen-only and excludes Shanghai listings, and omission skews the ranking toward money-market funds. `window` and the default `direction=in` are reinforced, though the underscore-prefixed plumbing params (`_jq`, `_spill`, `_fields`) are left entirely to the schema.

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?

The first clause names a specific verb and resource ('Ranks ETFs by estimated net creation/redemption in CNY') and scopes it to a '1/5/20 trading-day window'. It also explicitly frames the metric as an estimate with the formula, which separates it from a reported-flow or listing tool without opening any 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?

It gives strong conditional guidance: omitting `asset_class` lets money-market ETFs dominate, and `asset_class=equity` corrects that at the cost of dropping Shanghai-listed funds — a clear when-to-use/when-not tradeoff. It does not name a sibling alternative, but no other tool's behavior is inferred here, so the missing alternative reference is minor.

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