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_breadth

Intraday breadth time series for one trading day (240 minute bars; 13:00 excluded — ticks at the lunch-break boundary are too sparse). trade_date omitted = today (pre-open returns empty); explicit YYYY-MM-DD = historical replay. Returns per-minute rows of up/down/flat/limit_up/limit_down/breadth/divergence fields — full mode matches sentiment_overview; compact omits long summaries and extended breadth fields. Coverage reports source and returned time ranges. Budget trimming retains latest points, ascending.

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

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响应模式;REST/CLI 默认 full,MCP 默认 compact(导出除外)
last_nNo仅返回最近 N 个交易分钟点,午休不计入
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
trade_dateNoTrade date YYYY-MM-DD; omit for today
_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 supplied, the description carries the burden and does well: it discloses the 13:00 exclusion and why, the pre-open empty-return edge case, the returned per-minute field set, the coverage/time-range reporting, and the trimming policy ('retains latest points, ascending'). It does not cover error conditions or whether the call is strictly read-only, leaving some behavioral ground uncovered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the resource and granularity come first, then date semantics, then return shape, then trimming behavior. Every clause carries specific operational detail with no filler, appropriate for a 10-parameter tool with three enums.

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?

Covers what the schema cannot: the time-grid semantics, the empty-result boundary, the return field set (important since there is no output schema), and truncation behavior. The universe/scope filtering and the underscore-prefixed plumbing parameters are left entirely to the schema, which is acceptable given 100% 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 the baseline is 3; the description adds genuine meaning on top by explaining what trade_date omission does, what compact versus full actually drops, and what Coverage reports. It does not explain scope, last_n beyond the schema, or the underscore-prefixed controls, all of which the schema already documents.

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 verb+resource ('Intraday breadth time series for one trading day') with the exact granularity (240 minute bars) and even names the related sibling whose output full mode matches (`sentiment_overview`). An agent can tell what this returns and how it differs from the sentiment overview without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete selection conditions for the trade_date parameter (omitted = today, explicit = historical replay) and explains when to prefer compact vs full mode ('compact omits long summaries and extended breadth fields'). It stops short of naming an alternative tool to use for other needs, so it is a clear-context score rather than explicit when/when-not routing.

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