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

hot

SHAPE: data is a TOP-LEVEL ARRAY of {name, canonical_code, mention_count, latest_at} — no items wrapper (write [*].name). Stocks most mentioned by sell-side research notes; array order is the rank. mention_count is every mention in the window, not deduplicated. ⚠️ Sell-side attention, not retail — retail attention is social_hot; the two do not validate each other. HK names appear and can lead (HK: prefix). Window: trailing hours (default 24), or with date the previous trading day's 15:00 → that day's 15:00 (China time). ⚠️ Walk trading days, not calendar days — a weekend date returns a cumulative, overlapping window; drive the walk from trading_days. ⚠️ Windows differ in length (a Monday spans the weekend), so mention_count does not compare across days as-is; rank within a day does. An empty array means no mentions (failures return 503). History starts 2026-02-25 — earlier dates are not covered, not quiet.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
dateNoTrading day YYYY-MM-DD (China time). Window = previous trading day's close 15:00 → that day's close 15:00; mention_count is every mention inside it, counted in full. Omit for the rolling `hours` window ending now.
hoursNoRolling window in hours ending now (1-168, default 24). Ignored when `date` is given.
limitNoRows to return (1-100, default 20).
_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.6/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 most of it: empty array means no mentions, failures return 503, history starts 2026-02-25 (earlier dates are not covered, not quiet), and `mention_count` is not deduplicated. It also discloses that weekend `date` returns a cumulative overlapping window and that counts are not comparable across windows. Missing: read-only/side-effect confirmation and pagination behavior, though the surface is clearly a read.

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 return shape, then window semantics, then caveats — a logical order with no filler sentences. It is dense and warning-heavy (four ⚠️ blocks) but nearly every clause changes how the tool should be called or interpreted; a slight cost in scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only ranking tool with 9 params, no annotations and no output schema, the description fully covers return shape, field semantics, window behavior, empty-vs-error distinction, and coverage start date. Nothing an agent needs to call it correctly or interpret the result appears missing.

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 baseline is 3, but the description adds real meaning: it tells the agent the top-level array has no `items` wrapper, so `_fields`/`_jq` must be written as `[*].name` — while the schema's `_jq` example still says 'items[*].id', which is an internal inconsistency an agent must resolve. It also explains window-length asymmetry affecting `mention_count` but not within-day rank, which the schema does not. `limit` and `_spill`/`_max_bytes` are left to their schema text.

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?

Opens with 'SHAPE: `data` is a TOP-LEVEL ARRAY of {name, canonical_code, mention_count, latest_at}' and immediately defines the resource as 'Stocks most mentioned by sell-side research notes' with array order = rank. It explicitly distinguishes itself from the sibling `social_hot` (retail attention) and notes HK names can appear, so an agent can identify the tool without opening the schema despite the vague name 'hot'.

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

Usage Guidelines5/5

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

Gives explicit routing: sell-side attention here, retail attention is `social_hot`, and 'the two do not validate each other.' It also warns to walk trading days rather than calendar days and to drive that walk from `trading_days`, plus states when `date` overrides `hours`. This is close to full when/when-not/alternative coverage.

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