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

social_hot

Retail-attention leaderboard: A-shares retail investors are watching now, aggregated across several public attention boards. ⚠️ Retail board — hot is the sell-side board; they measure different populations and do not validate each other. score / mention_count are a weighted rank aggregate, not a count of posts and not comparable to hot. Array order is the rank. rank_change is versus one hour ago (null = not on the board then). ⚠️ Snapshot only, no history. Read computed_at / stale_seconds for freshness. Attention is not a bullish signal.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_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/5.0
Behavior5/5

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

With no annotations and no output schema, the description carries the full burden and does so: it discloses that results are a one-hour snapshot with no history, points to `computed_at` / `stale_seconds` for freshness, explains array order is rank and `rank_change` is versus one hour ago with null meaning absent. It even pre-empts a likely misinterpretation ('Attention is not a bullish signal'), which materially affects how an agent reports results.

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?

Front-loaded with purpose, then caveats in descending priority, with zero filler sentences. Every clause conveys a distinct constraint (population distinction, score semantics, ordering, rank change, staleness, interpretation warning).

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?

Because there is no output schema, the description must define return-field meaning itself, and it does for `score`, `mention_count`, `rank_change`, `computed_at`, `stale_seconds`, and array order. Nothing an agent needs in order to call this and interpret the result correctly appears to be missing.

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% and all six parameters are generic envelope controls (`_jq`, `_spill`, `_fields`, `_intent`, `_max_bytes`, `_max_bytes_mode`) already documented in the schema. The description adds no parameter-level guidance such as which `_fields` are worth projecting for this endpoint, so the 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?

The description opens with a specific verb+resource phrase: a retail-attention leaderboard of A-shares investors' current watchlists, aggregated across public attention boards. It explicitly names the sibling `hot` and states the different population it measures, so an agent can distinguish the two 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?

It gives a clear selection rule against the main alternative (`hot` is the sell-side board; the two do not validate each other), which is exactly the routing decision an agent faces. It also warns 'snapshot only, no history', implying history needs must go elsewhere, though it does not name the tool to use for that.

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