Skip to main content
Glama

Ashares Quote

ashares_quote
Read-onlyIdempotent

Real-time quote(s) for Chinese A-share stocks by 6-digit code (Shanghai 6xxxxx, Shenzhen 0xxxxx/3xxxxx, STAR 688xxx, ChiNext 30xxxx, Beijing 8xxxxx/4xxxxx). Returns name, current price, change and change %, open, previous close, day high/low, volume, turnover, and the quote timestamp. Accepts one code or a comma-separated list. Example: ashares_quote({ symbols: "600519,000858" }) for Kweichow Moutai and Wuliangye. Volume is reported in whole 100-share lots. 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": {
      "symbols": "600519"
    },
    "name": "ashares_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesOne 6-digit code or a comma-separated list, e.g. "600519" or "600519,000001,300750". sh/sz/bj prefixes are accepted but optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "symbols": "600519"
      +  },
      +  {
      +    "symbols": "600519,000858,300750"
      +  }
      +]
  2. First observed

TDQS

A4.2/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, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (Tencent Finance, keyless so no auth setup), the enumerated return fields, and the non-obvious fact that volume is in whole 100-share lots.

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 the core purpose and exchange mapping, then return fields, then the example. Every sentence carries information, though the worked example ('Kweichow Moutai and Wuliangye') partly duplicates the examples already in the schema.

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, so enumerating the returned fields (name, price, change %, open, previous close, high/low, volume, turnover, timestamp) is exactly the right compensation. Combined with source, batching support, and the volume-unit caveat, an agent has everything needed to call and interpret the result.

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 baseline is 3, but the description adds meaning the schema lacks: the digit-prefix-to-exchange mapping (6xxxxx Shanghai, 0xxxxx/3xxxxx Shenzhen, 688xxx STAR, etc.) and a concrete multi-symbol example. That extra mapping helps an agent validate and construct symbols.

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 quote(s) for Chinese A-share stocks') and immediately scopes it with the 6-digit code format and exchange-by-prefix mapping. An agent can distinguish this from historical or snapshot siblings without opening the schema.

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 word 'Real-time' implies this is the current-price tool versus historical siblings like ashares_daily_history, and the example shows an intended call. However, it never explicitly says when to prefer this over ashares_market_snapshot or ashares_intraday_bars, so routing is left to inference.

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.