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_clock

按显式 market 查询市场阶段,当前仅接入 HK,CN/US 预留且不回退。含半日市、竞价、午休及人工例外;省略 at 使用服务端当前时间。at 必须带时区,返回所选市场的 IANA 时区时间。trading_profile=index 只表示相关市场阶段,指数计算时段未核验。午间扩展交易须提供有已核验资格的证券代码。actual_end_unknown=true 表示随机结束时点未知,null 表示日历或阶段未知;不存在的具体证券返回 security_not_found;市场阶段不证明个股未停牌。

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_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo带时区时刻,例如 2026-12-24T12:08:30+08:00
_jqNoJMESPath,对 data 求值(写 items[*].id)
micNoISO 10383 交易场所代码,HK 省略时取 XHKG;未来 US 按场所选择日历
codeNo港股或已注册指数规范代码;省略为市场规则模板
_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 保留前缀
trading_profileNo证券、指数或经核验的午间扩展交易equity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 well: it discloses the no-fallback rule for CN/US, the server-time default, the mandatory timezone on `at`, the IANA timezone of the returned times, and the meaning of actual_end_unknown (true vs null). It also warns that a market phase does not prove a security is trading, and names security_not_found. Auth, rate limits and return shape are unaddressed but are largely non-applicable or low-risk for a read-only clock.

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 action and the HK-only constraint, then the time semantics, then caveats. It is dense and heavily semicolon-chained, so it reads as a spec dump rather than prose, but nearly every clause carries information an 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 an 11-parameter tool with no output schema, the description covers the important unknowns: market support, time handling, output flags (actual_end_unknown), and an error case. The 6 helper parameters (_jq, _spill, _fields, _max_bytes, etc.) are left entirely to their schema descriptions, which is acceptable given full coverage.

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 a 3 is the baseline, but the description genuinely adds meaning the schema lacks: omitting `at` means server current time, `at` must carry an offset, and trading_profile=index only signals the market phase without verifying index calculation windows. It also ties `code` to the verified-eligibility requirement for midday extended trading.

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 concrete verb and resource ("按显式 market 查询市场阶段") and immediately narrows scope: only HK is live, CN/US are reserved. An agent knows what it retrieves and which markets work. It does not name any sibling (e.g. market_status, market_calendar) to distinguish itself from, which is the only thing keeping this from a 5.

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 real selection rules: omit `at` to use server time, supply a verified `code` for midday extended trading, and expect market_not_supported for CN/US rather than a fallback. It stops short of explicitly routing the agent to an alternative tool when HK isn't the target market.

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