Skip to main content
Glama

wmshare_quote

Fetch current or intraday quotes for one or multiple symbols in the same market, automatically batching multiple requests. Supports CN, HK, and US markets with live or snapshot output.

Instructions

取一只或多只同市场标的的最新/盘中报价;多只自动批量。

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": {
      "symbols": "<symbols>"
    },
    "name": "wmshare_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNotrue=盘中最新;false=最近快照
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolsYes同市场标的列表;多只自动批量,不要逐票循环
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses only the batching trait. Nothing is said about permissions, rate limits, per-call symbol caps, partial-failure behavior, or what happens with mixed-market input - all material for a live-quote call.

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?

A single front-loaded sentence with two clauses, zero filler, and the resource stated before the operational hint. Nothing could be cut without losing meaning.

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 a five-parameter read tool with full schema coverage and an output schema, the description is close to sufficient: purpose, market scoping, and batching are all present. Gaps around mixed-market handling and result limits are minor given the rich schema.

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%, so live/market/output/max_rows semantics are already documented in the schema. The description adds only the 'same market' constraint and batching hint, which is the baseline expectation 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.

Purpose4/5

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

The description names a specific verb and resource (fetch latest/intraday quotes) plus scope (one or more symbols in the same market) and the batching behavior. It implicitly separates itself from history-style siblings via '最新/盘中', but never names an alternative explicitly.

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 '多只自动批量' clause gives one actionable usage rule - pass a list rather than looping per symbol - which is real guidance. There is no statement of when not to use this tool or which sibling to prefer for historical, cross-market, or screening needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.