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

market_indices

按显式 market 查询指数目录,当前仅接入 HK,CN/US 预留且不回退。港股包含:恒生、国企、恒生科技、红筹、综合指数。items 行标识为 canonical_code;registry_revision 为随代码维护的注册表版本,不能视为实时行情源日期。quote_enabled/chart_enabled=false 表示报价和图表未启用。

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": {
      "market": "<market>"
    },
    "name": "market_indices"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_spillNotrue=全量落盘,只回摘要与取数地址
marketYes必填市场范围:CN/HK/US。本组端点当前仅接入 HK;CN/US 不回退港股,返回 market_not_supported;原有 A 股端点保持兼容
_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

A3.6/5.0
Behavior3/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 add real value: row identity via canonical_code, the warning that registry_revision is a code-maintained registry version and not a quote date, and the meaning of quote_enabled/chart_enabled=false. However, the no-fallback / market_not_supported behavior is already spelled out in the market parameter's schema text, so part of the disclosure is duplication rather than added insight.

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 the core query statement, then supporting caveats about coverage, row identity, and revision semantics. It is dense and mostly earns its space, though the CN/US no-fallback clause repeats the schema verbatim.

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?

No output schema exists, so the description responsibly explains the key returned fields (canonical_code, registry_revision, quote_enabled/chart_enabled). For a 7-parameter catalog tool the definition is adequate, though it does not outline the remaining row fields an agent would receive.

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% and the market enum is fully documented in the schema, including the CN/US behavior. The description adds no parameter-level meaning (e.g., interaction of _fields with items rows) beyond what the schema already states, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (查询/query) and resource (指数目录/index catalog) scoped to an explicit market, and enumerates the HK index families it returns, so an agent can distinguish this catalog lookup from quote-oriented siblings. It stops short of naming any sibling tool to route against.

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?

Gives clear usage context: pass an explicit market, only HK is currently served, CN/US are reserved with no fallback to HK. That functions as an implicit when-not, but no explicit alternative endpoint is named for CN/US needs.

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