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

fundflow

Minute-by-minute capital flow for one A-share, split by order size: main force (super + big), super, big, normal, small, retail. Amounts are CNY; positive = net inflow. *_cum fields are running totals for the day — never sum them across bars; *_delta is the per-bar change and is what you sum. Shanghai and Shenzhen only, from 2026-05-26; intraday it runs to the latest completed minute. Use it to tell whether a move is carried by large orders or by retail, and to spot late-session accumulation a daily number hides.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesSingle canonical code (e.g. SSE:600519)
dateNoTrade date YYYY-MM-DD (default: today, Beijing time)
_spillNotrue=全量落盘,只回摘要与取数地址
_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/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 most of it well: it discloses the sign convention (positive = net inflow), the currency, the critical distinction that `*_cum` fields are running totals that must not be summed while `*_delta` is the per-bar change to sum, the supported exchanges, the 2026-05-26 start date, and intraday freshness. It omits permissions, rate limits, and any response envelope detail, so it is not fully self-sufficient.

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?

Purpose is front-loaded in the first clause, followed by units and sign convention, then the cumulative-versus-delta trap, then scope limits, then intended use. Every sentence carries distinct information and nothing is restated from the input 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 eight-parameter tool with no output schema and no annotations, the description covers the highest-risk gaps: what the numbers mean, how to aggregate them correctly, and what universe and time range are valid. It is slightly incomplete in that it never sketches the returned row shape beyond the `*_cum`/`*_delta` naming convention, and the exchange restriction silently conflicts with the schema's accepted code pattern.

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%, so the baseline is 3 and the schema already documents every parameter in detail. The description does add meaningful meaning by narrowing the `code` parameter to a single Shanghai/Shenzhen listing, which is narrower than the schema's regex that also permits BSE/BJ. It says nothing about the seven underscore-prefixed plumbing parameters, leaving that entirely to the schema.

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 — minute-by-minute capital flow for one A-share — and enumerates the order-size buckets (main force, super, big, normal, small, retail). An agent can tell exactly what data comes back. It does not explicitly distinguish itself from concept-level fund flow siblings such as concepts_fundflow_minute, so it stops short of a 5.

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 decision context: use it to judge whether a move is carried by large orders or by retail, and to spot late-session accumulation a daily number hides. That is real when-to-use guidance. It gives no when-not-to-use or named alternative, which keeps it at 4.

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