Skip to main content
Glama

Hk Quote

hk_quote
Read-onlyIdempotent

Real-time quote(s) for Hong Kong-listed stocks by HKEX code. Answers 'Tencent stock price', '腾讯股价', '00700 quote', 'HSBC Hong Kong share price'. Accepts one code or a comma-separated list, in any common form (700, 00700, 0700.HK). Returns English and Chinese name, price, change and change %, open, previous close, day high/low, volume, turnover in HKD, P/E, and the 52-week range. If you have a company NAME rather than a code, call hk_resolve_symbol first. Example: hk_quote({ codes: "00700,00005" }) for Tencent and HSBC. Source: Tencent Finance (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": {
      "codes": "00700"
    },
    "name": "hk_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYesOne HKEX code or a comma-separated list, e.g. "00700" or "700,5,9988". Accepts 0700.HK form too. Max 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description adds the data source (Tencent Finance) and that it is keyless, which tells the agent no auth is required. It also discloses the exact returned fields, so the agent knows what data will come back. The only gap is freshness/latency and rate-limit behavior, which 'real-time' only gestures at.

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 and scope, then routing guidance, then return fields, then an example call — a sensible information hierarchy with no filler. It is somewhat dense and repeats code formats already present in the schema, but the example query phrasings earn their space for retrieval matching.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the returned fields (names, price, change, OHLC-ish values, volume, turnover in HKD, P/E, 52-week range). Combined with source disclosure and the sibling routing rule, nothing an agent needs to call it correctly is missing.

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% and the schema already documents the comma-separated list, accepted forms like 0700.HK, and the max of 30. The description largely restates those accepted forms plus an example call, so it adds little meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 and resource: real-time quotes for Hong Kong-listed stocks by HKEX code. It also names the sibling it is not for name-based lookups (hk_resolve_symbol), so an agent can distinguish the two without opening 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?

Explicitly routes the agent: use this when you have a code, and call hk_resolve_symbol first if you have a company name. It further anchors usage with realistic query phrasings ('Tencent stock price', '腾讯股价', 'HSBC Hong Kong share price'), covering both English and Chinese intents.

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.