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

auction

Opening call auction (集合竞价) as its own dataset — today or any past trading day. Items: canonical_code, name, auction_price (= the official open), prev_close, pct_change (points), volume (shares), amount (CNY). stage: final = settled result (after the 09:25 match; backfilled for history) / live = today 09:15–09:25 from the live snapshot — before 09:25 that is the INDICATIVE price, volume/amount null (nothing traded yet). Auction leaderboard: sort=pct_change + limit (order=asc for the weakest); watchlist: codes. Empty with a note on non-trading days or before the dataset starts. 竞价未匹配量 unmatched 为股,正买负卖;unmatched_as_of 是最后有效竞价观测的源时间(09:25 后冻结),历史未采集为 null。

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
sortNoRanking key applied before limitpct_change
codesNoComma-separated canonical codes (max 500); omit for the whole market
limitNoMax rows after sorting
orderNodesc (default) or asc
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
trade_dateNoYYYY-MM-DD; omit for today
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 a lot: it distinguishes `stage=final` (settled after the 09:25 match, backfilled for history) from `stage=live` (today 09:15–09:25), warns that before 09:25 `live` is INDICATIVE with `volume`/`amount` null, and states that results are empty with a `note` on non-trading days. It also documents `unmatched` sign convention and that `unmatched_as_of` freezes after 09:25. It does not mention response-size/truncation behavior, which a caller would need to reason about for large limits.

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?

The description is front-loaded with the dataset definition, then the field list, then stage semantics, then usage recipes — a logical order with little filler. It is dense rather than bloated, though the trailing Chinese sentence on unmatched volume is hard to parse for a non-Chinese reader and slightly disrupts an otherwise tight structure.

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?

There is no output schema, so the description has to explain return shape, and it does: it enumerates `canonical_code`, `name`, `auction_price`, `prev_close`, `pct_change`, `volume`, `amount`, plus `stage`, `unmatched`, and `unmatched_as_of`. Combined with null-behavior and empty-result notes, an agent has enough to call this and interpret the result correctly.

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 all 11 parameters, and the baseline of 3 applies. The description reinforces meaning for `sort` (leaderboard ranking) and `codes` (watchlist scoping) but adds no format or edge-case detail beyond the schema's own enum and description text.

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 opening line names the specific resource and scope: 'Opening call auction (集合竞价) as its own dataset — today or any past trading day.' That is a concrete noun plus scope, not a restatement of the tool name, and it tells an agent exactly which dataset it retrieves.

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?

It gives concrete recipes: 'Auction leaderboard: `sort=pct_change` + `limit` (`order=asc` for the weakest); watchlist: `codes`.' That maps intents onto parameter combinations, which is genuine usage guidance. It stops short of naming a sibling tool to use instead when something other than auction data is wanted, so it is clear context without explicit exclusions.

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