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

quote

Real-time quote for 1-200 A-share securities (last price, volume, change %, bid/ask). For >200 codes use scan. HK codes are not supported; for an A+H company use the A-share canonical (SSE:601398, not HK:01398). Rows also carry turnover_rate (percent), same_minute_volume_ratio (cumulative shares through the snapshot minute divided by the five-session same-minute cumulative-share average; null if missing; not comparable to market turnover volume_ratio), fundflow_latest {trade_date, bar_time, main_net_cum, super_net_cum} (latest stored minute cumulative CNY; check its date/time), industry (Shenwan L1/L2), top_concept (strongest member concept now) and, for margin-list names, a T+1 margin block. Expect industry / top_concept to be absent on many rows — coverage, not failure: top_concept resolves for only a subset of A-shares and industry does not cover 北交所 (BSE:*). top_concept is not the limit-up LLM leading_concept, which is not served here. Live rows also expose top_base_concept {id,name,kind:base,pct_change} and top_concept_status / top_base_concept_status (ready, no_membership, no_snapshot, unavailable). The two layers rank independently; use kind=base for base detail. Historical rows carry neither current theme field nor their statuses. In pre_open / auction sessions read the auction block {status, prev_close, price, pct_change, volume, amount}, not top-level price / pct_change. status is not_started / matched / no_match; a top-level pct_change of 0 in that window is ambiguous — only auction.status = matched with auction.pct_change = 0 is a flat auction. 盘前顶层 prev_close 与 auction.prev_close 对齐为今日基准,prev_close_date 为上一交易日;previous_close 为昨日实际收盘价。prev_close_basis 区分交易所参考价、事件调整价与未校准昨收,prev_close_provisional=true 时不可视为已确认除权参考价。未撮合的顶层 price 仅为基准展示,pct_change 为 null。 Suspended / frozen names report no_match; auction.volume / amount stay null until the 09:25 match (volume in shares). Read market_trade_date, not snapshot_at, to tell whether a row is today's. Unknown codes are omitted; known-but-unmatched codes come back with null prices. super_net_in 为最新已存分钟累计超大单净流入(元),时间与 fundflow_latest 相同。 main_net_in = current-day cumulative main-capital net inflow (CNY; main_net_in_stale = fallback layer, not necessarily previous-day data; check fundflow_latest.trade_date/bar_time; null for BSE:*). 竞价未匹配量 unmatched 为股,正买负卖;unmatched_as_of 是最后有效竞价观测的源时间(09:25 后冻结),历史未采集为 null。

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>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codesYesArray of canonical codes (e.g. ['SSE:600519', 'SZSE:000001'])
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
include_l2NoInclude L2 5-level order book (requires quote:l2 scope)
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so thoroughly: unknown codes omitted vs known-but-unmatched returning null prices, suspended/frozen names reporting `no_match`, auction volume/amount null until the 09:25 match, and expected absence of industry/top_concept (with the BSE coverage gap explained as coverage rather than failure). It also flags stale-data checks (fundflow_latest date/time, prev_close_provisional) and the L2 scope requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose and the 200-code limit are correctly front-loaded, but the body is a dense run-on that hops between field definitions, session semantics and Chinese-only notes, mixing languages mid-paragraph. Some guidance repeats (the fundflow_latest date/time check appears twice), and a bulleted field list would carry the same content more cheaply.

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 must explain the response, and it does: it enumerates the special fields, their units, their nullability and their coverage limits, plus session-dependent semantics and the market_trade_date vs snapshot_at distinction. An agent has enough to interpret rows correctly in every session state.

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 description coverage is 100%, so the baseline is 3, but the description adds genuine meaning for `codes`: canonical exchange-prefixed format, the 200-code ceiling, HK exclusion, and which canonical to pick for dual-listed names. The `_jq`/`_spill`/`_fields`/`_max_bytes` plumbing params are left entirely to the schema.

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?

Opens with a concrete verb+resource: real-time quote for 1-200 A-share securities, plus the exact fields returned (last price, volume, change %, bid/ask). It immediately bounds scope and names `scan` as the sibling for larger batches, so the agent can distinguish it without opening a schema.

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?

Explicit routing rules: use `scan` for more than 200 codes, HK codes unsupported, use the A-share canonical code for A+H companies, and in pre_open/auction sessions read the auction block rather than top-level price. It does not route to the separate `auction` or snapshot sibling tools, leaving that choice implicit.

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