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

concepts_alerts

Currently active concept alerts. Two rules: big_move (|pct_change| > 3%) and limit_up_cluster (limit_up_count >= 3 AND stock_count >= 5). Cheap, non-billable. Use as the agent's signal for 'which themes are running hot right now'. With kind=industry, only big_move ever fires — a Shenwan level-1 industry holds 150+ members, so the limit-up cluster rule would trigger nearly every day and drown the feed.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
kindNoDimension: concept (hot-theme library, default), base (broad base labels), or industry. All use independent chain-linked equal-weight indices with base 1000. A stored theme membership alone does not establish current trading activity; use concept_tags for current status.concept
_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
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the two firing rules with thresholds, states the call is 'cheap, non-billable' (important cost context), and warns that kind=industry suppresses limit_up_cluster because level-1 industries hold 150+ members. It says nothing about return shape or volume of alerts.

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?

Purpose and rules are front-loaded, then cost, then the kind=industry caveat. Dense but every sentence carries information; the industry explanation is slightly verbose but justified by preventing a bad feed.

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?

For a read-only alert feed with no output schema and 7 largely infrastructural params all documented in the schema, the description covers purpose, trigger conditions, cost, and the key parameter quirk. Only the shape of an individual alert and expected volume are left implicit.

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 beyond the schema: it explains that kind=industry materially changes which rules can fire, which the enum description alone does not convey.

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 the resource (currently active concept alerts) and enumerates the exact triggering rules for big_move and limit_up_cluster, which is far more precise than the bare name. It stops short of naming a sibling to contrast with (concept_tags appears only in the schema, not the description), so it is not fully differentiated.

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?

'Use as the agent's signal for which themes are running hot right now' gives a clear use case, and the industry caveat tells the agent when a particular configuration is degenerate. No explicit when-not-to-use or named alternative appears in the description itself.

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