Skip to main content
Glama

Hk Resolve Symbol

hk_resolve_symbol
Read-onlyIdempotent

Find the HKEX stock code for a company by name, the lookup step before hk_quote. Answers 'what is Tencent's Hong Kong ticker', 'Xiaomi HK code', 'Alibaba Hong Kong listing'. Returns ONLY Hong Kong-listed equities: derivative warrants, CBBCs and non-HK listings (ADRs, US/Frankfurt lines) are excluded, and each match states the code it resolved to so you can confirm it is the company you meant before quoting it. Source: Yahoo Finance search (Latin names), Tencent Finance symbol search (Chinese names), keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Tencent"
    },
    "name": "hk_resolve_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name, in English or Chinese, e.g. "Tencent", "小米", "HSBC".
limitNoMax matches to return, 1-10 (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max matches to return, 1–10 (default 5)."New value: +"Max matches to return, 1-10 (default 5)."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (read-only, idempotent, open-world, non-destructive), the description discloses the coverage boundary (HK-listed equities only, derivatives excluded), the upstream data sources split by script, the fact that no API key is required, and that each match echoes the resolved code so the caller can verify before quoting.

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?

It is front-loaded with the verb-and-resource statement, then exclusions, then return behavior, then data provenance – a sensible ordering. The list of three illustrative questions slightly duplicates the schema's own examples, which is the only real slack.

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?

With no output schema, the description carries the burden of describing returns, and it does so at a high level ('each match states the code it resolved to'). It stops short of describing zero-match behavior or how the limit interacts with ranked results, which would matter for a lookup whose whole job is disambiguation.

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% and both parameters are documented in the schema, so the baseline is 3. The description nonetheless adds real meaning to 'name' by revealing that Latin names are routed to Yahoo Finance and Chinese names to Tencent Finance, which tells the agent the romanization of the input actually matters.

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 and resource ('Find the HKEX stock code for a company by name') and explicitly positions itself relative to a sibling ('the lookup step before hk_quote'). The three quoted example queries make the intended question shape unambiguous.

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?

It clearly states when to reach for this tool (name-to-ticker lookup ahead of quoting) and what it explicitly will not return (warrants, CBBCs, ADRs, US/Frankfurt lines). It does not, however, contrast itself with the other resolution-style sibling such as resolve_entity, so an agent facing a generic entity lookup gets no routing guidance.

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.