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

global_index_snapshot

Snapshot for 30 global equity indices plus Hong Kong indices (e.g. 日经225 GIDX:NKY, 标普500 GIDX:SPX, 纳斯达克 GIDX:IXIC, 恒生指数 HKEX:HSI). A-share indices are index_snapshot. These markets span time zones — always read data_tier: realtime = trading now; closed / warm / daily / stale_cache = a previous close, never report as live; unavailable = no data. is_stale is true for everything except realtime; meta.realtime_count / meta.closed_count give the split. market_trade_date is each market's LOCAL trading day — never compare it with a Beijing date. volume null = not published.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codesNoCanonical codes to narrow the snapshot (e.g. ['GIDX:NKY', 'HKEX:HSI']); omit for all 30
_spillNotrue=全量落盘,只回摘要与取数地址
regionNoFilter by region; combine with `codes` to narrow further. Omit for all regions
_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.3/5.0
Behavior5/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 so well: it enumerates the data_tier values and their meanings, states that is_stale is true for everything except realtime, points to meta.realtime_count/meta.closed_count, warns that market_trade_date is a local trading day that must not be compared with a Beijing date, and notes that a null volume means unpublished. These are exactly the interpretation rules an agent cannot infer from the schema.

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?

Front-loaded with scope and the sibling exclusion, then the data_tier interpretation rules, which are the highest-risk failure mode. It is dense and slightly run-on in the middle, but nearly every clause prevents a concrete misuse; nothing reads as 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?

There is no output schema, so the description must explain return semantics, and it covers the critical fields (data_tier, is_stale, meta counts, market_trade_date, volume). It stops short of describing the overall response envelope or how codes/region narrowing affects the returned set, which would have closed the remaining gap.

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 eight parameters including codes, region, _jq, _spill and _max_bytes. The description adds only the incidental facts that the universe is 30 indices and the code format, matching the schema's own pattern. Baseline 3 is appropriate where the schema does the heavy lifting.

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 resource and scope — a snapshot of 30 global equity indices plus Hong Kong indices — and gives concrete code examples (GIDX:NKY, HKEX:HSI). It also explicitly excludes A-share indices and names the sibling that serves them (index_snapshot), so an agent can route correctly 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?

The A-share exclusion routes the agent to `index_snapshot`, and the data_tier guidance tells the agent how to interpret and how not to report results (never report a previous close as live). It does not state when to prefer this over other snapshot siblings such as concepts_snapshot, but the resource scope is narrow enough that this is a minor gap.

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