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

sentiment_overview

Aggregate sentiment for one trading day's latest minute: up/down/flat, limit-up/down, gt3/lt3 breadth, divergence index + label, MA20/50/200 breadth, 52w new highs/lows. Omit trade_date for today realtime. Also a leverage block (融资融券): judge by exchanges.financing_net_buy_cny, never gross financing_buy_cny; structure.avg_maintenance_ratio below 1.3 = forced-liquidation line. The leverage block is T+1 — not the same day as the rest — and each sub-block has its own as_of. leverage null = unavailable. Also a turnover block (current_turnover / predicted_total / delta_vs_yesterday, same numbers as sentiment_turnover's header) — no second call needed for 成交额. turnover.volume_trend = expanding (放量) / contracting (缩量) / flat vs the previous two sessions at the same minute (vs_prev_2d_ratio, per-day prev_sessions[]); read it instead of comparing against yesterday's full-day total.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
scopeNoUniverse filter: all_a | all_a_ex_st (default, ex-ST + ex-newly-listed) | st_only | main_board | star_market | chinext | bse. The four boards sum exactly to all_a_ex_st.all_a_ex_st
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
trade_dateNoTrade date YYYY-MM-DD; omit for today realtime
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the `leverage` block is T+1 and therefore not the same day as the rest, that each sub-block has its own `as_of`, that a null `leverage` means unavailable, and that `financing_net_buy_cny` must be used instead of gross `financing_buy_cny`. The 1.3 maintenance-ratio forced-liquidation line is a disclosed interpretation threshold. It says nothing about response size limits or failure behavior, though the `_spill`/`_max_bytes` params hint at truncation.

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 contents, then the two caveat blocks most likely to cause misreads (T+1 leverage, turnover duplication). Dense backtick-heavy prose but nearly every clause carries an operational warning or a routing instruction; the block-by-block ordering mirrors the response shape.

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?

With no output schema, the description must describe returns, and it does so by enumerating every block and its fields, plus a data-lag caveat and an interpretation rule for the volume trend. Remaining gaps are interpretive rather than blocking: how the divergence index label should be read and what thresholds apply to up/down breadth.

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 all eight parameters (including `scope` with its board-sum constraint, `_jq`, `_fields`, `_spill`) are already documented in structured form. The description's only parameter-side addition is the realtime-when-omitted rule for `trade_date`, which the schema already states verbatim. Baseline 3 applies.

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 (aggregate sentiment for one trading day's latest minute) and enumerates exactly which metric families are returned: up/down/flat counts, limit-up/down, gt3/lt3 breadth, divergence index + label, MA20/50/200 breadth, 52w highs/lows, plus `leverage` and `turnover` blocks. An agent can distinguish this from `sentiment_breadth` or `sentiment_premium` without opening the 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?

"Omit `trade_date` for today realtime" and "no second call needed for 成交额" give concrete call-time routing, and the latter explicitly steers the agent away from calling `sentiment_turnover` for the same numbers. It also tells the agent to read `turnover.volume_trend` rather than hand-comparing against yesterday's full-day total. It stops short of stating when to prefer `sentiment_breadth`/`sentiment_pct_distribution` over this overview for narrow questions.

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