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

trading_days

Trading days that have a hot-stock board, newest first, as {dates:[...]} (China time). Use this to drive a date walk over hot — never iterate calendar days: a weekend hot date returns a cumulative window that re-counts notes, whereas these days tile with no overlap and all have data. days looks back in CALENDAR days (7-365); coverage begins 2026-02-25. ⚠️ A coverage index for the research board, NOT an exchange calendar — use market_status for whether the market is open.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trading_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoLook-back in calendar days (7-365, default 90). Only trading days with data are returned.
_spillNotrue=全量落盘,只回摘要与取数地址
_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.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden and does well: it reveals the coverage start date (2026-02-25), the no-overlap/tiling property, and the failure mode of using calendar days against `hot`. It does not mention pagination, rate limits, or auth needs, so it stops 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences: purpose and output shape first, then the driving guidance, then the caveat and alternative. Warnings are inline and every clause carries operational information; there is no restatement of the name or filler.

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 7-parameter read with no output schema, the description supplies the return shape, time basis, and coverage floor, which is what an agent needs to call it correctly. Minor gaps remain around what happens when `days` extends past the 2026-02-25 coverage start, but nothing essential is missing.

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, but the description adds a genuinely useful nuance by stressing that `days` is measured in CALENDAR days (7-365) and by tying the window to the coverage start date. That clarifies the most likely misinterpretation (assuming `days` counts trading days) beyond what the schema alone conveys.

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?

The description states a specific resource (trading days that have a hot-stock board), an ordering (newest first), and the exact return shape `{dates:[...]}` in China time. It also explicitly negates a sibling role ("NOT an exchange calendar — use `market_status`"), so an agent can distinguish it from `market_status` 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?

It gives explicit when-to-use ("Use this to drive a `date` walk over `hot`"), an explicit prohibition ("never iterate calendar days"), the reason (a weekend `hot` date returns a cumulative window that re-counts notes, whereas these days tile with no overlap), and a named alternative (`market_status`) for a different question. That is a complete routing decision.

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