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_show

Detail for one concept: meta plus current member securities with latest snapshots. Use after concepts_list. Pass kind=industry for a Shenwan industry id — a dimension mismatch returns 404, same as an unknown id. Members carry close / pct_change plus price (identical to close, the name quote / scan use for the last price). The response echoes kind; carry it with the id. Members are ordered by main_net_in desc by default (who is drawing money in); change with member_sort / member_order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "concept_id": "<concept_id>"
    },
    "name": "concepts_show"
  }
}

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
concept_idYesConcept primary key (PG concepts.id)
member_sortNoOrder members by: main_net_in (default) / pct_change / amount / weight; members missing the key go lastmain_net_in
member_orderNodesc (default) or ascdesc
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 disclosure burden. It does well on error semantics (dimension mismatch returns 404) and response shape (echoes kind, member fields), but a 10-parameter read tool would benefit from stating whether the read is side-effect free and any limits on member count or snapshot freshness.

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 core purpose before the caveats, and the parenthetical asides (price/close aliasing, 'who is drawing money in') each add real disambiguation value. Slightly dense with four separate qualified statements, but no sentence is pure filler.

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 tool with 10 parameters, no output schema and no annotations, the description covers the essentials: what the payload contains, how members are ordered, the dimension/404 trap, and the kind echo needed for follow-up calls. Remaining gaps are return-size limits and helper-parameter behavior, which the schema partly documents.

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 baseline is 3. The description does go further by explaining that member_sort=main_net_in means 'who is drawing money in', how to change ordering, and that kind selects a dimension, but it says nothing about the helper parameters (_jq, _fields, _spill, _max_bytes).

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?

States a specific verb and resource ('Detail for one concept') plus exactly what comes back: meta plus current member securities with latest snapshots. It also positions itself relative to a named sibling ('Use after concepts_list'), so an agent can distinguish it without opening the 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?

Gives a clear sequencing rule (call after concepts_list) and a concrete dimension rule: pass kind=industry for a Shenwan industry id, with a mismatch yielding 404 just like an unknown id. What's missing is an explicit when-not-to-use / 'use X instead' alternative for the member-level data, though it does point at concept_tags for current trading status.

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