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

bars_batch

Batch K-line for multiple A-shares in one round-trip. Daily bars default to date desc; use order=asc for chronological calculations. Response sort echoes the date order. Daily: ≤100 codes × ≤1 yr; minute: ≤20 codes × ≤7 d. Envelope: {items:[{canonical_code, bars}], errors:[{canonical_code, error_code, message}]}. ⚠️ Read errors[] first: an unknown code lands there as unknown_security, while a real security with no trading in the window returns an empty bars[] — report that as no data, not a bad code.

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": {
      "codes": "<codes>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "bars_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesInclusive end date YYYY-MM-DD
_jqNoJMESPath,对 data 求值(写 items[*].id)
fromYesInclusive start date YYYY-MM-DD
codesYesCanonical codes (daily ≤100; minute ≤20)
orderNoDaily bar date order (default desc); minute bars are always ascending
_spillNotrue=全量落盘,只回摘要与取数地址
minuteNoMinute-level bars instead of daily (tighter caps apply)
_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.1/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 it well: it discloses default sort direction, that response sort mirrors the requested order, per-mode size caps, the response envelope shape, and the critical distinction between unknown_security and an empty bars array. It omits any mention of permission requirements, rate limits, or what happens when the code cap is exceeded (error vs silent truncation).

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 front-loaded with purpose, then defaults, caps, envelope shape, and the errors-first warning in a logical progression. It is dense but nearly every clause carries operational value; 'Response sort mirrors the date order' slightly repeats the preceding sentence.

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?

For an 11-parameter tool with no output schema and no annotations, the description supplies the response envelope, the error taxonomy, the caps, and the default behaviors an agent needs. Very little is left to guesswork.

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 the baseline is 3. The description adds meaning the schema does not state: the ≤1 yr daily window and ≤7 d minute window, and the practical consequence of order=asc. Those are real additions beyond the enum and maxItems declarations.

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 first sentence gives a specific verb and resource: batch-fetching K-line bars for multiple A-shares in one round-trip. The word 'Batch' implicitly distinguishes it from single-code charting tools, but no sibling is named, so an agent must infer the boundary itself.

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?

Concrete guidance is given for the order parameter (asc default, asc for chronological calculations), for daily vs minute mode through the size caps, and for interpreting errors[]. No explicit 'use X instead when Y' routing to alternatives such as chart or concepts_daily_bars is provided.

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