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_turnover

Intraday turnover time series with current_turnover / predicted_total / delta_vs_yesterday headline fields, plus volume_trend (expanding 放量 / contracting 缩量 / flat) and vs_prev_2d_ratio vs the previous two sessions at the same minute. trade_date omitted = today (pre-open returns nulls); explicit YYYY-MM-DD = historical. days (1-5) pulls that day + N-1 prior trading days for same-minute YoY comparison.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNotrade_date 当日 + 之前 days-1 天(1-5,默认 1)
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
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose real behavior: the null-return edge case pre-open, the meaning of the volume_trend states (expanding/contracting/flat), and that vs_prev_2d_ratio is measured at the same minute across the prior two sessions. It says nothing about result size, pagination, or how scope interacts with the series.

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?

Three tight sentences, front-loaded with the return payload before parameter behavior. No filler, though the inline Chinese glosses for the volume_trend enum values add visual noise for an English-language agent.

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 nine parameters, no annotations and no output schema, the description compensates well by naming the headline fields and the comparison basis. What is missing is the series granularity (minute vs tick) and whether scope changes the aggregate meaning, so it is strong but not airtight.

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 still adds meaning the schema does not: that days drives a same-minute year-over-year style comparison against N-1 prior trading days, and that the omitted trade_date path returns nulls before the open. That extra context justifies one point above baseline.

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 specific verb+resource: an intraday turnover time series, and enumerates the headline fields it returns (current_turnover, predicted_total, delta_vs_yesterday, volume_trend, vs_prev_2d_ratio). This makes it clearly distinct from sibling sentiment tools like sentiment_breadth or sentiment_overview, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied through parameter semantics: omit trade_date for today's session, supply YYYY-MM-DD for historical, raise days to bring in prior sessions for comparison. There is no explicit when-not guidance, no named alternative tool, and no statement of what to do when the pre-open null case occurs.

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