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_status

Current A-share session state. session ∈ pre_open (09:00-09:14) / auction (09:15-09:29) / open / break (lunch) / closed, same enum as quote. Read session, not is_market_open / is_premarket — both are false at lunch AND after the close. trade_date is today's China calendar date, not the trading day — qualify with is_trading_day; next_trading_day null = calendar not populated (unknown). is_holiday marks shut weekdays only (weekends read false). Free — call before quote / bars to choose pre-market vs intraday vs after-close behaviour.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_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.4/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 substantial work: it flags that `is_market_open`/`is_premarket` are false at lunch AND after close, that `trade_date` is the China calendar date rather than the trading day, that `next_trading_day` null means the calendar is unpopulated (unknown, not "no next day"), and that `is_holiday` only marks shut weekdays. It also states the call is free. The only gap is the absence of any note on response shape beyond the field list or on failure behavior.

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?

Purpose is front-loaded and every clause carries non-obvious information — the enum ranges, the field-routing warning, and the three semantic caveats. The telegraphic backtick-and-em-dash style packs a lot in, but the density of traps in a few sentences makes it slightly harder to parse on first read than a plainly structured version.

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 convey the return fields, and it names the decision-relevant ones (`session`, `trade_date`, `is_trading_day`, `next_trading_day`, `is_holiday`, plus the two misleading booleans). Combined with the enum ranges and the pre-quote timing advice, an agent has everything needed to call this correctly and interpret the result.

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% — all six parameters (`_jq`, `_spill`, `_fields`, `_intent`, `_max_bytes`, `_max_bytes_mode`) are documented in the schema itself, and they are generic envelope controls rather than tool-specific inputs. The description adds no parameter guidance, so the baseline 3 applies; nothing is missing but nothing is added.

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?

The opening line names a specific resource and scope ("Current A-share session state") and immediately enumerates the `session` enum values, so an agent knows exactly what is returned. It also anchors the enum to a sibling ("same enum as `quote`"), making the relationship explicit without needing to open either 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?

The final sentence gives concrete timing guidance — "call before quote / bars to choose pre-market vs intraday vs after-close behaviour" — naming the tools it precedes and the decision it enables. It also routes the agent away from the wrong fields ("Read `session`, not `is_market_open` / `is_premarket`"), which is stronger than generic when-to-use advice.

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