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

etf_list

Directory of A-share ETFs: manager, tracked index, tick size, daily limit band. Filter by index_code (000300 or SSE:000300), q (name/ticker substring) or asset_class. For a fund's own numbers use etf_show. ⚠️ asset_class is only published for Shenzhen-listed funds — filtering by it drops every Shanghai one. ⚠️ limit_pct null = band unknown, not unbanded. price_tick is 0.001 (a tenth of the stock tick).

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

Input Schema

NameRequiredDescriptionDefault
qNoSubstring over Chinese name and ticker
_jqNoJMESPath,对 data 求值(写 items[*].id)
limitNoMax items (default 50)
_spillNotrue=全量落盘,只回摘要与取数地址
offsetNoPagination offset
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
index_codeNoTracked index code, bare ('000300') or prefixed ('SSE:000300')
asset_classNoShenzhen-only classification; drops all Shanghai funds when set
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 does disclose real data-semantics behavior: asset_class coverage is Shenzhen-only, a null limit_pct means 'band unknown' rather than 'unbanded', and price_tick is 0.001 rather than the stock tick. It stops short of describing pagination defaults or response shape, but the schema already documents limit/offset/_spill/_jq.

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, then filters, then the sibling routing, then two clearly marked caveats. It is dense but every clause carries information; the only waste is the index_code and asset_class phrasing that duplicates the schema text.

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?

There is no output schema, so the description usefully summarizes what a row contains and flags the two traps (Shenzhen-only asset_class, null limit_pct) that would otherwise produce bad downstream reasoning. For an 11-parameter read-only listing tool whose schema is fully documented, that is close to sufficient.

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 coverage is 100%, so the baseline is 3, and most of the description's parameter text restates the schema verbatim ('index_code' bare vs prefixed, 'q' as name/ticker substring, asset_class dropping Shanghai funds). The genuinely additive part — null limit_pct semantics and the tick-size value — describes output fields rather than the 11 input parameters, and 8 of those parameters get no description-level treatment at all.

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/resource hybrid ('Directory of A-share ETFs') and enumerates the fields returned (manager, tracked index, tick size, daily limit band). It explicitly contrasts itself with 'etf_show' for 'a fund's own numbers', so an agent can pick between the two without inspecting 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?

Names the three filter dimensions and gives the concrete selector that routes elsewhere ('For a fund's own numbers use etf_show'). It also supplies a when-not-to-filter warning for asset_class, telling the agent that using that filter silently excludes all Shanghai-listed funds.

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