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_list

List concepts with a live snapshot (pct_change / index_value / up_count / down_count / limit_up_count / amount / speed_3min). Default sort pct_change desc; order=asc gives the bottom-N instead (e.g. today's worst concepts). All sort keys (pct_change / amount / main_net_in / limit_up / speed / stock_count) rank the whole universe before limit, so the result is a true top-N (or bottom-N); concepts missing the sort key always go last. Entry point for browsing; drill in with concepts_show / concepts_daily_bars. Every item echoes kind (concept / base / industry) — pass it along with the id, since by-id verbs default to kind=concept and an industry id without it returns 404. During 09:00–09:14 values are the previous close (note says so).

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

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
sortNoSort field: pct_change / amount / main_net_in / limit_up / stock_count / speedpct_change
limitNoMax items (1-1000, default 500)
orderNodesc (default) = top-N; asc = bottom-N, e.g. the concepts falling hardest todaydesc
_spillNotrue=全量落盘,只回摘要与取数地址
statusNoConcept status filteractive
_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.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose several non-obvious traits: sorting applies to the whole universe before `limit` so results are a true top-N, items missing the sort key always sort last, passing `kind` is mandatory or an industry id returns 404, and values are previous-close between 09:00–09:14. However it says nothing about pagination, response envelope, or empty-result behavior for an 11-parameter tool, so coverage is strong but not complete.

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 purpose and return fields, then the sort/limit contract, then the sibling routing note, then the staleness caveat — a sensible order with no filler sentences. It is dense with semicolons and parentheticals, and the `order=asc` explanation partially duplicates the schema's own enum description.

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 an 11-parameter, zero-required listing tool with no annotations and no output schema, the description covers the critical semantics: ranking scope, tie-breaking, kind echoing, and intraday staleness. Gaps are the default/active `status` filtering behavior and any guidance on result size or pagination, though `limit` and `status` remain documented in the schema.

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 adding semantics the schema lacks — that `order=asc` yields the bottom-N rather than a reversed listing, that sorting happens pre-limit, that missing sort keys are placed last, and that `kind` must be echoed to by-id verbs. The `_jq` / `_spill` / `_fields` utility parameters and `status` are left entirely to the schema.

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 a specific verb+resource ("List concepts") and immediately enumerates the snapshot fields returned (pct_change / index_value / up_count / down_count / limit_up_count / amount / speed_3min). It also distinguishes itself from siblings by naming concepts_show and concepts_daily_bars as drill-down targets, so an agent can place it without opening any schema.

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?

Explicitly frames the tool as the "entry point for browsing" and routes deeper lookups to concepts_show / concepts_daily_bars. It also states when to use the non-default mode ("order=asc gives the bottom-N instead (e.g. today's worst concepts)"), leaving no ambiguity about top-N vs bottom-N selection.

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