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

security_reference

按规范代码查询证券参考详情,当前仅接入港股,CN/US 预留:ISIN、币种、每手股数、双柜台关联及身份核验状态。source 包含来源、版本、源日期、观测时间和最后成功检查时间;stale=null 表示未知。collection_eligible 仅为参考资格,不代表报价已启用。listing_status/trading_status=unknown 不可解释为正常交易。

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYes规范证券代码,例如 HK:00700 或 US:AAPL;由前缀确定市场,当前详情仅接入 HK
_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.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose important interpretive caveats: stale=null means unknown, collection_eligible is reference eligibility only and does not mean quotes are live, and listing_status/trading_status=unknown must not be read as normal trading. What it omits is operational behavior — latency, auth requirements, rate limits, or what a not-yet-supported market returns — leaving the mutation/caching/error profile undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by market coverage, then field-level semantics for source/stale/collection_eligible/status. Every sentence carries distinct information, and the caveats are separated by semicolons rather than buried in prose.

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?

Seven parameters, one required, no output schema and no annotations — so the description must supply return-value semantics, and it does: it enumerates the fields returned (ISIN, currency, lot size, dual-counter linkage, identity verification status) and defines the ambiguous ones (source components, stale=null, collection_eligible, unknown statuses). The main remaining gap is error/empty-result behavior for non-HK codes.

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 3 baseline would apply on parameter documentation alone. The description earns above that by clarifying the market prefix semantics beyond the pattern: codes may carry SSE/SZSE/US prefixes but only HK is actually served today, which materially changes how an agent should form the `code` argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause states a specific verb and resource, '按规范代码查询证券参考详情' (look up security reference details by canonical code), and immediately bounds scope with '当前仅接入港股,CN/US 预留'. An agent knows exactly what it gets and for which markets. It stops short of 5 because no sibling tool or alternative data source is named for comparison.

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?

The description gives a real usability constraint — only HK details are live, CN/US codes are accepted but reserved — which effectively tells the agent when this call will return meaningful data. However it never states when not to use this tool or which sibling (e.g. bars/quote-style tools) to prefer for pricing data, so route guidance is only implied.

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