Skip to main content
Glama

wmshare_history

Retrieves daily K-line history for a stock symbol using either recent bar count or paired begin/end dates, with optional adjustment and sample, count, or summary output for CN, HK, and US markets.

Instructions

取个股日 K:支持 n、前/后复权和 begin/end 区间;begin/end 必须成对。

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": {
      "symbol": "<symbol>"
    },
    "name": "wmshare_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo最近 K 线根数;与 begin/end 二选一
adjNo复权:qfq 前复权或 hfq 后复权
endNo日期,格式 YYYY-MM-DD
beginNo日期,格式 YYYY-MM-DD
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolYes标的代码;先用 wmshare_symbols 解析
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
Behavior3/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; it does disclose the pairing constraint for begin/end, which is real behavioral information. However, it stays silent on defaults inherited from server config (market), truncation at the 200-row cap, and the output-mode switch, leaving key behavioral traits to the schema.

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?

A single compact clause chain with the core capability front-loaded and no filler. It is efficient, though it spends its limited length on parameters rather than on routing or behavior.

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

Completeness3/5

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

The tool has 8 parameters, cross-market behavior defaulting to server config, and three output modes; the description addresses only the window and adjustment aspects. An output schema exists so return values need not be described, but the caller still lacks enough context for the market/output/max_rows surface.

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 the baseline is 3. The description adds the begin/end pairing rule and enumerates the adjustment and window options, but does not explain market, output, max_rows, or how 'n' interacts with begin/end beyond the pairing note.

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 states a specific verb and resource ('取个股日 K' — fetch daily K-lines for a single symbol) and names the main knobs (n, adjustment, begin/end range). It does not distinguish itself from siblings such as wmshare_quote, but the resource is concrete enough for an agent to know what it returns.

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?

It gives one hard usage rule (begin/end must appear together, with n as the alternative) but no guidance on when to choose this over wmshare_quote or wmshare_intl, nor any prerequisite beyond what the schema's symbol description mentions.

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