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_of

Which themes does this stock belong to? Inverse of concepts_show: returns a security's active concepts (id, name, today's percent change). Pass code (preferred; lookup first if you only have a name) or query (substring over name/ticker, may match several — read each canonical_code); at least one. ⚠️ A concept with null name and pct_change exists but has no snapshot yet. ⚠️ kind returns one dimension: concept (hot-theme library, default), base (base labels), or industry — carry the dimension with each id. ⚠️ An empty array means no recorded membership in this dimension. Use concept_tags for both layers, coverage states and currently active themes.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeNoCanonical code, exact (e.g. SSE:600519). Preferred over `query` when resolved.
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
limitNoMax matched securities (1-20, default 10). Caps securities, not concepts per security.
queryNoSubstring over security name or ticker (e.g. 宁德时代 / 300750). May match several.
_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.4/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 burden and mostly delivers: it discloses the return fields, warns that a concept with null `name`/`pct_change` has no snapshot yet, explains that `kind` returns only one dimension and the dimension must be carried with each id, and states that an empty array means no recorded membership. It stops short of stating the read-only nature explicitly or any calling limits, which keeps it just under a 5.

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 question and answer shape before caveats, and every sentence contributes a rule or edge case. The warning-glyph formatting is dense but readable; a slightly tighter structure would earn a 5.

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 a 10-parameter, no-annotation, no-output-schema tool, the description covers the domain parameters and edge cases well, but it says nothing about the generic infrastructure parameters (`_jq`, `_spill`, `_fields`, `_max_bytes`) and does not describe response envelope shape beyond the concept fields. Adequate but with visible gaps given the tool's complexity.

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, but the description adds real meaning on top: `code` is preferred over `query`, `query` matches substrings across name/ticker and may return multiple securities whose `canonical_code` must be read individually, and `kind` selects exactly one dimension whose label must be carried with each returned id. These are disambiguation rules the schema alone does not state.

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 direct question that names the resource relationally ("Which themes does this stock belong to?") and then states the exact operation: returns a security's active concepts with id, name, and today's percent change. It explicitly frames itself as the inverse of `concepts_show`, so an agent can pick between 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: pass `code` when resolved, call `lookup` first if you only have a name, and fall back to `query` with a caveat that it may match several and each `canonical_code` must be read. It also names the sibling to use instead (`concept_tags`) for both layers and current active themes, which is a clear when-not-this-tool statement.

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