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_history

Concept-alert historical events (default last 24h). Filter by rule (big_move / limit_up_cluster) and Unix-ms from/to window. Used by AI agent / admin to review what fired and when.

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

Input Schema

NameRequiredDescriptionDefault
toNoUnix ms; default = now
_jqNoJMESPath,对 data 求值(写 items[*].id)
fromNoUnix ms; default = now - 24h
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
ruleNoFilter by alert rule
limitNoMax items (1-2000, default 500)
_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

B3.4/5.0
Behavior3/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. It does disclose the default 24h lookback and that this is a retrieval of past events (read-only by implication), which is useful. It says nothing about ordering, pagination beyond the schema's limit, or how many events are typically returned, leaving real behavioral gaps for a no-annotation tool.

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 short sentences, front-loaded with the resource and default scope, then filters, then audience. Nothing is padded. The final sentence is somewhat low-value ('used by AI agent / admin') relative to the two before it, keeping it just below top marks.

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

Completeness3/5

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

For an 11-parameter query tool with no annotations and no output schema, the description covers the domain semantics but omits return shape, ordering, and the behavior of the cross-cutting `_jq` / `_spill` / `_fields` parameters (though those are documented per-parameter). It is minimally adequate rather than complete.

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%, so the schema already documents `rule`, `from`, `to`, `kind`, and `limit` including their defaults. The description echoes the `rule` enum values (big_move / limit_up_cluster) and the Unix-ms window semantics, adding modest emphasis but no genuinely new meaning. Baseline 3 is appropriate where the schema does the heavy lifting.

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 specific resource and scope: historical concept-alert events, defaulting to the last 24h. An agent can immediately tell this is a lookback/audit query rather than a live alert feed. It stops short of naming the sibling tool (concepts_alerts) that presumably returns current state, so differentiation is implicit rather than stated.

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?

"Used by AI agent / admin to review what fired and when" gives an implied use case plus a stated default window, which is helpful. However, there is no explicit when-not guidance and no named alternative for querying active/current alerts or for other filtering dimensions. The agent must infer that this tool is the historical counterpart of concepts_alerts.

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