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_daily_bars

Daily OHLC for a concept index (chain-linked equal-weight, base 1000). Returns breadth fields and is_backfilled flag. 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_daily_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesInclusive end date YYYY-MM-DD
_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

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the required `bars:read` scope and the 404 semantics, but it omits any statement about response size limits, truncation/spill behavior, or backfill implications even though `is_backfilled` is called out without explanation of what a backfilled bar means for analysis.

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?

Three sentences, front-loaded with what is returned, then the `kind` caveat, then the auth requirement. Nothing is padded, though the `is_backfilled` mention without explanation is a slightly wasted clause.

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?

With no output schema, the description does the necessary work of naming the return payload (OHLC plus breadth fields and a backfill flag), and it covers auth. For a 10-parameter tool it is reasonably complete, with the main gap being the absence of guidance on the pagination/truncation parameters.

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 coverage is 100%, so the baseline is 3. The description adds real meaning to `kind` by tying a wrong dimension to a 404 rather than an empty result, but the other nine parameters — including the generic `_jq`, `_spill`, `_fields`, and byte-limit controls — receive no treatment at all.

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 verb and resource: daily OHLC bars for a concept index, with the index methodology (chain-linked equal-weight, base 1000) named. An agent can distinguish this from minute-bar siblings by the 'daily' qualifier, though no sibling is named explicitly.

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 a clear conditional rule for `kind=industry` and explains the 404 failure mode on a dimension mismatch, which is genuinely useful routing guidance. It does not say when to prefer this over concepts_minute_bars or concepts_snapshot, so usage is only partially framed.

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