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_show

One ETF's profile plus its latest daily row: close, shares outstanding, unit NAV, premium/discount, estimated net creation. ⚠️ Two premium fields, not interchangeable: premium_rate_same_day only when the NAV date equals the trade date; premium_rate_ref falls back to the latest NAV (date in premium_ref_nav_date) — cross-border ETFs publish NAV late, so ref is not same-day. Both are ratios (0.012 = 1.2%), not percentage points. ⚠️ accum_nav is not on the same basis as unit_nav after a share conversion — do not compare or derive returns. quality / inputs_mask say which inputs were present; latest null = no row yet.

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": {
      "code": "<code>"
    },
    "name": "etf_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesCanonical code, e.g. SSE:510300
_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

A3.9/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 real work: it warns that `premium_rate_same_day` and `premium_rate_ref` are not interchangeable, that cross-border ETFs publish NAV late, that values are ratios not percentage points, and that `accum_nav` is not on the same basis as `unit_nav` after a share conversion. It does not state side effects, read-only nature, or rate/latency characteristics, which keeps it from 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?

Content is front-loaded with purpose before the field caveats, and every sentence addresses a real misinterpretation risk. It is dense and warning-symbol-heavy, making it slightly harder to scan than it needs to be, but there is little 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 no output schema, the description covers the highest-risk semantics of the returned row and the `quality`/`inputs_mask`/`latest`-null edge cases. It does not describe the overall response envelope or how the query-control parameters affect the returned shape, leaving a modest gap for a 7-parameter tool.

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 `code` pattern, `_jq`, `_spill`, `_fields`, `_max_bytes`, and `_max_bytes_mode` are all already documented. The description adds no parameter-level guidance (e.g., format examples beyond the schema, when to use `_spill` for large responses), so the baseline of 3 applies.

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?

The description opens with a specific verb+resource+scope: 'One ETF's profile plus its latest daily row', then enumerates the returned measures (close, shares outstanding, unit NAV, premium/discount, estimated net creation). The singular 'One ETF' scoping naturally separates it from list/flow siblings such as etf_list and etf_flows without ambiguity.

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?

Usage is only implied: an agent can infer this is the single-ETF lookup rather than a list or flow tool, and that a canonical code is needed. No explicit when-to-use, when-not-to-use, or named alternative is provided, and error cases (unknown code, no row yet) are only partially covered by the note that `latest` may be null.

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