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

concepts_fundflow_minute

Minute-by-minute capital flow for a concept or industry, summed over its current active constituents — the same basis as main_net_in in concepts list. Same field semantics as the per-security fundflow verb: *_cum are running day totals (never sum across bars), *_delta is the per-bar change. Amounts are CNY, positive = net inflow. Each bar carries covered_members, how many constituents had data by that minute. Pass kind=industry when the id is a Shenwan industry. Use it to see whether a theme is being accumulated or distributed while it moves.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
dateNoTrade date YYYY-MM-DD (default: today, Beijing time)
kindNoDimension: concept (hot-theme library, default), base (broad base labels), or industry. All use independent chain-linked equal-weight indices with base 1000. A stored theme membership alone does not establish current trading activity; use concept_tags for current status.concept
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
concept_idYesConcept primary key
_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 load and does so well: it discloses that bars are minute-level, that `*_cum` are running day totals that must never be summed across bars, that `*_delta` is per-bar change, that amounts are CNY with positive = inflow, and that `covered_members` reports late-arriving constituent coverage. The 'current active constituents' basis is a meaningful survivorship caveat. Missing are any statements on read-only safety, rate limits, or failure modes.

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?

Roughly five sentences, each front-loaded with a distinct fact (scope, field semantics, units/sign, coverage caveat, parameter routing, use case). Nothing is redundant and the aggregation-basis caveat arrives before the detail.

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?

There is no output schema, so the description must explain the return shape — and it does, covering `*_cum`, `*_delta`, `covered_members`, units, and sign convention. For a read-only minute-series tool, that plus the constituent-basis caveat covers what an agent needs to call it correctly and interpret results.

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 schema already documents all nine parameters including the `kind` enum and `concept_id`. The description adds only one extra mapping — the coupling of `kind=industry` to a Shenwan industry id — and says nothing about `_jq`, `_fields`, `_spill`, or `_max_bytes`. That is marginally above the baseline, not substantially so.

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 ('Minute-by-minute capital flow for a concept or industry') plus an explicit aggregation basis (summed over current active constituents). It also pins itself against siblings by naming `concepts list`'s `main_net_in` and the per-security `fundflow` verb, so an agent can distinguish it 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?

Gives an explicit routing rule for a parameter ('Pass `kind=industry` when the id is a Shenwan industry') and a use case ('see whether a theme is being accumulated or distributed while it moves'). It does not state when to prefer a sibling such as per-security `fundflow` or `concepts_minute_bars` instead, which keeps it below a 5.

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