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

chart

Single-security K-line for stocks and A-share indices (daily by default; minute=true + one date for intraday). Multi-code: bars_batch (stocks only). Indices are detected from the code: SSE:000xxx, SZSE:399xxx, BSE:899xxx. ⚠️ The exchange prefix decides it — SSE:000001 is the Shanghai Composite, SZSE:000001 is 平安银行; pass kind to override. To measure a stock against its market, call twice over the same window (stock + index) — index_snapshot has no history. Index minute bars are capped at 7 calendar days. Indices add pct_change and have no turnover-rate or market-cap field.

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

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD inclusive end (daily mode; overrides days)
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesSingle canonical code — stock (e.g. SSE:600519) or A-share index (e.g. SSE:000001, SZSE:399006, BSE:899050)
dateNoSingle trade date YYYY-MM-DD (minute mode)
daysNoDaily lookback (ignored when from/to or minute mode are set)
fromNoYYYY-MM-DD inclusive start (daily mode; overrides days)
kindNoOverride the stock/index guess made from the code. Omit unless the code is one the rule gets wrong — SSE:000xxx / SZSE:399xxx / BSE:899xxx are read as indices, everything else as stocks.
_spillNotrue=全量落盘,只回摘要与取数地址
minuteNoSwitch to minute-level bars (requires date)
_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/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 well: it discloses the 7-calendar-day cap on index minute bars, that indices add pct_change and lack turnover-rate/market-cap fields, and that the exchange prefix determines stock vs index. It omits error behavior, rate limits, and return shape, keeping it short of a 5.

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 with the core purpose, then caveats and routing. Dense but nearly every clause carries information; the backtick-heavy formatting and emoji warning are slightly noisy but not wasteful.

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 13-parameter tool with no output schema and no annotations, the description covers the main modes, index detection, and key data caveats. The generic plumbing parameters (_jq, _spill, _max_bytes) are left to the schema, which is acceptable.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: minute=true requires a single date, kind overrides the prefix-based guess, and days is the daily lookback. It explains the intent behind parameters rather than restating them.

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+resource (single-security K-line for stocks and A-share indices), the default mode (daily), and the intraday variant. It explicitly distinguishes itself from siblings bars_batch (multi-code, stocks only) and index_snapshot (no history), so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing: multi-code goes to bars_batch, and measuring a stock against its market means calling twice over the same window because index_snapshot has no history. It also names the condition for the kind override (only when the code-prefix rule misreads).

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