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

index_snapshot

Real-time snapshot for the 172 A-share indices with a live quote feed (e.g. 上证指数 SSE:000001, 深证成指 SZSE:399001, 创业板指 SZSE:399006, 科创50 SSE:000688, 北证50 BSE:899050): price, pct_change, amount, speed_3min per index, refreshed ~15s during market hours (last intraday snapshot outside trading hours). Pass codes to narrow to a subset; omit for all 172. Use this for 'how is the broad market doing right now' — quote covers individual stocks only. CSI-series indices (CSI:*) have no live feed and are not returned.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codesNoCanonical index codes to narrow the snapshot (e.g. ['SSE:000001', 'BSE:899050']); omit for all 172
_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 supplied, the description carries the burden and does well: it discloses the ~15s refresh cadence during market hours, the stale/last-snapshot behavior outside trading hours, and the fixed 172-index universe. It stops short of describing error behavior for invalid codes or how large responses are returned (the schema's 50KB `_max_bytes` default hints at size concerns the description never addresses).

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?

One dense paragraph that front-loads the resource and coverage, then the return fields, then refresh semantics, then the routing rule and exclusion. No filler sentences; every clause adds a fact the agent needs.

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-only snapshot tool with no output schema, the description covers scope, return fields, freshness, and routing adequately. The only gap is the generic JMESPath/spill/byte-limit parameters, which the description never touches — though the schema documents them.

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 real meaning: it explains that omitting `codes` yields all 172 indices, supplies concrete canonical code examples, and clarifies that CSI:* codes are valid-looking yet excluded from results — information not derivable from the schema pattern alone.

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 and resource (real-time snapshot of the 172 A-share indices with a live feed), enumerates returned fields, and explicitly distinguishes itself from `quote` (individual stocks) and from CSI-series indices that are not covered. An agent can identify the tool without opening the schema.

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 an explicit selection rule ("Use this for 'how is the broad market doing right now'"), names the alternative tool that handles the other case (`quote` covers individual stocks only), and states the parameter choice (pass `codes` to narrow, omit for all 172) plus a hard exclusion for CSI:* codes.

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