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_digest

One call for the whole board: session, 6 core indices, breadth + turnover, limit-up premium & ladder (with promotion rate), top concepts / industries and top 10 stocks by pct_change / main_net_in. Every list is {items}, fixed length — use the single verbs for longer lists. mode + trade_date say which day: before 09:15 or on a non-trading day it is the last session's close; 09:15–09:29 top_pct_change ranks the auction. Empty lists carry empty_reason; failed blocks are null + meta.partial_failures.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
scopeNoScope for breadth and turnover (same as sentiment_overview)all_a_ex_st
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
trade_dateNoHistorical YYYY-MM-DD; live-only blocks then come back not_covered
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does so well: fixed-length lists, `empty_reason` on empty lists, null blocks plus `meta.partial_failures` on failure, and live-only blocks returning `not_covered` for historical dates. It omits auth/rate-limit behavior and does not describe the `mode` value set, leaving some operational gaps.

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 payload inventory, then temporal semantics, then output-shape caveats — a sensible order with no filler sentences. It is dense to the point of being telegraphic (parentheticals, backticked jargon, semicolon chains), which slightly hurts first-pass readability.

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 8-parameter composite tool with no annotations and no output schema, the description covers the return envelope (fixed-length items, empty_reason, partial_failures) and date semantics adequately. Missing pieces are the `mode` enum values and any note on cost/latency for a board-wide call.

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: `mode` + `trade_date` jointly determine which session is returned, with distinct pre-open, auction-window, and non-trading-day behavior. Notably `mode` is referenced in prose but absent from the schema properties, so the description is doing compensatory work rather than repeating structured data.

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 (the whole board) and enumerates exactly what it contains: session, 6 core indices, breadth + turnover, limit-up premium & ladder, top concepts/industries, top 10 stocks by `pct_change` / `main_net_in`. An agent can distinguish this composite snapshot from the single-purpose siblings 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?

Gives an explicit when-not rule — 'Every list is `{items}`, fixed length — use the single verbs for longer lists' — and clarifies day-selection semantics (pre-09:15 / non-trading day = last close; 09:15–09:29 = auction ranking). It does not name the specific alternative verbs, so routing is clear in principle but not by name.

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