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_premium

SHAPE: two curves main[] and compare[] (not bars / items), rows {bar_time, avg_pct, stock_count}, plus main_pool_size / compare_pool_size. Are yesterday's limit-up buyers making money today? Yesterday's limit-up pool (minus one-word boards and boards that broke and stayed broken), plotted minute by minute today as an equal-weighted average percent change; compare is the same curve one day earlier. ⚠️ Read main_pool_size / compare_pool_size with the curves — they tell a premium move from a population change. ⚠️ Equal-weighted, not cap-weighted, so not comparable to index returns. Series use 240 minute end labels (09:31-11:30, 13:01-15:00). Pool dates are trading days, resolved server-side. Empty main with a non-zero pool size = session not started. Optional scope filters both pools; omit it to preserve the legacy all_a basket. ETF is excluded.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
scopeNoStock basket; all_a includes ST, all_a_ex_st excludes ST and newly listed stocks. Defaults to all_a for compatibility.
_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/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and it does so well: it discloses equal-weighted vs cap-weighted (hence not comparable to index returns), the need to read `main_pool_size`/`compare_pool_size` alongside the curves to separate a premium move from a population change, server-side trading-day date resolution, the 240-minute end-label convention, ETF exclusion, and the not-started edge case.

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?

Dense but nearly every clause carries information, and the warning markers correctly front-load the shape and the two chief misinterpretation risks. The only structural nit is that it opens with output shape rather than with what the tool answers, and the telegraphese (backticks, braces, 240-minute label ranges) assumes a fluent reader.

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?

There is no output schema, yet the description fully specifies the return shape, row fields, pool-size fields and edge cases, which is exactly what an agent needs here. The remaining gap is whether this always compares the latest two sessions or accepts a historical reference date – the description implies 'today vs yesterday' only.

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 earns above that by explaining that `scope` filters both pools and that omitting it preserves the legacy all_a basket – behavior the schema enum text does not state. The transport parameters (`_jq`, `_spill`, `_max_bytes`, `_intent`) are left entirely to the schema.

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?

The description states a concrete computation – yesterday's limit-up pool plotted minute-by-minute today as an equal-weighted average percent change, with the prior day as `compare`. That is far more specific than the bare name, but it is framed as a question plus data-shape notes rather than a verb+resource statement, and it never names a sibling (e.g. sentiment_breadth) to distinguish itself from.

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?

When-to-use is only implied by the tightly scoped question it answers; there is no explicit comparison against sentiment_breadth / sentiment_overview / sentiment_pct_distribution. The one usage instruction present is parameter-level: omit `scope` to preserve the legacy all_a basket, and treat empty `main` with a non-zero pool size as 'session not started'.

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