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_minute_bars

Concept-index minute-level OHLC (chain-linked equal-weight, base 1000). Minute-end labels, 240 bars per full session (09:31-11:30, 13:01-15:00); boundary bars are merged preserving volume and amount. Max 7 days per request. Pass kind=industry when the id is a Shenwan industry — a dimension mismatch returns 404, same as an unknown id. Requires bars:read scope.

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>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "concepts_minute_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesInclusive end date YYYY-MM-DD (max 7 days)
_jqNoJMESPath,对 data 求值(写 items[*].id)
fromYesInclusive start date YYYY-MM-DD
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

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does so well: it discloses bar labeling (minute-end), session boundaries (09:31-11:30, 13:01-15:00), 240 bars per full session, and the non-obvious boundary-bar merge rule that preserves volume and amount. It also discloses the auth requirement ('Requires `bars:read` scope') and the 404 failure mode for dimension mismatches. What it omits is the response shape and ordering, which matters given no output schema.

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?

It is a dense, front-loaded block with no filler sentences: definition, session mechanics, request limit, dimension routing, and scope each occupy one clause and earn their place. The trade-off is that technical details (240 bars, merge behavior) are packed tightly, but nothing is redundant.

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 read-only bar-fetching tool with 10 parameters (mostly generic projection/limit controls like `_jq`, `_fields`, `_max_bytes`), the description covers data semantics, session mechanics, request size limits, error behavior, and scope requirements. The main remaining gap is that, with no output schema, it never sketches what a bar record contains or how results are ordered.

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 every parameter including the kind enum semantics and the per-parameter date patterns; the baseline is therefore 3. The description adds one genuinely new piece of meaning beyond the schema: a dimension mismatch on `kind` returns 404 identically to an unknown id, which tells the agent how to interpret failures. The rest, including the 7-day limit, largely restates what the `to` parameter description already says.

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?

The description states a specific resource and granularity: 'Concept-index minute-level OHLC (chain-linked equal-weight, base 1000)'. An agent immediately knows this returns minute bars for concept indices, not daily bars or fundflow. It does not explicitly name the sibling concepts_daily_bars as the daily alternative, so the differentiation is inferable from 'minute-level' rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives one conditional usage rule ('Pass `kind=industry` when the id is a Shenwan industry') and a hard constraint ('Max 7 days per request'), which steers parameter choice well. However, it never names an alternative tool (concepts_daily_bars for daily resolution, concept_tags for current membership) or states when this tool is the wrong choice, so the tool-selection guidance is only implied.

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