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

lookup

SHAPE: {matches: [{canonical_code, name_cn, ticker, exchange}], count} — the row container is matches, not items, and the name field is name_cn. Resolve a Chinese name / A-share code / pinyin initials to canonical codes (e.g. SSE:600519). Use this first whenever the agent has a description but needs a canonical_code for downstream calls. AH dual-listing: when a company is listed on both A-share and HK (e.g. 工商银行 SSE:601398 / HK:01398), prefer the A-share canonical for all downstream analysis unless the user explicitly asks for the HK side.

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": {
      "text": "<text>"
    },
    "name": "lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
textYesSearch text: Chinese name (贵州茅台), code (600519), or pinyin (gzmt)
limitNoMax matches (1-30)
_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 and no output schema, the description carries the full burden and does disclose the response envelope, including the non-obvious detail that the row container is `matches` rather than `items` and the name field is `name_cn`. It also states a default resolution policy for dual-listed names. It omits nothing fatal but says nothing about no-match results, auth, or rate limits.

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?

Two dense sentences with no filler; the response-shape warning is front-loaded precisely because there is no output schema. It is slightly over-technical in spelling out `{matches: [{canonical_code, name_cn, ticker, exchange}], count}` inline, but that earns its place as a recurring agent mistake.

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 an 8-parameter tool with no output schema, the description covers the three things an agent can't get elsewhere: return shape, when to call it first, and A-share vs HK preference. Missing only edge-case behavior such as empty result sets or whether HK matches are returned at all.

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%, with every parameter (including the _jq/_spill/_fields/_max_bytes plumbing) documented in the schema itself. The description only restates the accepted input formats for `text` (Chinese name, code, pinyin) and adds no syntax detail beyond the schema's example. Baseline 3 is appropriate.

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 second sentence states a specific verb and resource: "Resolve a Chinese name / A-share code / pinyin initials to canonical codes (e.g. SSE:600519)." That distinguishes it from the announcements/bars/concepts siblings, which all consume codes rather than produce them. The vague tool name "lookup" and the fact that the response-shape sentence is front-loaded keep it from a 5.

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?

"Use this first whenever the agent has a description but needs a canonical_code for downstream calls" gives an explicit trigger condition, and the AH dual-listing rule ("prefer the A-share canonical ... unless the user explicitly asks for the HK side") resolves a real ambiguity. No when-not or failure-path guidance (e.g. no match) is given.

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