Skip to main content
Glama

wmshare_market

Retrieve minute bars, money flow, margin, convertible bond, index, valuation history, and full security universe data across CN, HK, and US markets for market screening and analysis.

Instructions

取 1 分钟分时、资金流、两融、可转债、指数、估值历史和证券全集。

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": {
      "domain": "<domain>",
      "action": "<action>"
    },
    "name": "wmshare_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo历史窗口条数
endNo日期,格式 YYYY-MM-DD
keyNo指数键;members/weights/valuation 需要
trigNo可转债强赎触发价,元
beginNo日期,格式 YYYY-MM-DD
levelNo行业目录层级
top_nNo指数成员/权重返回条数
actionYesdomain 下的动作;运行时会校验合法组合
domainYes市场数据域:分钟/资金流/两融/转债/指数/估值/证券全集
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
metricNo估值历史指标;金融/亏损股建议 pbpe
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
pointsNo指数估值时序采样点数
symbolNo标的代码;全集/转债全市场/指数 keys 可空
windowNo估值历史窗口,最大 3y3y
sort_byNo指数成分排序字段
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full burden by itself, yet it says nothing about read-only behavior, authentication needs, rate limits, or return size. The meaningful behavioral constraints, namely max_rows hard limit 200, output modes sample/count/summary, and the 3y valuation window cap, appear only in the schema. For a tool with 17 parameters and 20 actions, that omission is a serious gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, and the domain list is front-loaded. However, it is concise by omission rather than effective tailoring: it merely echoes the domain enum and omits what the agent most needs, namely the relationship between action and domain.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. Even so, a tool with two required enum parameters and 15 optional parameters, spanning 7 domains and 20 actions, needs much more than a one-line domain list. The description leaves the core invocation model, namely which action belongs to which domain, undocumented.

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 description coverage is 100%, with every one of the 17 parameters documented in the schema, including enum values and defaults. The description adds no meaning beyond that; it does not explain key-parameter dependencies such as key being needed for members/weights/valuation, or when to choose metric pb. With the schema doing all the work, the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description starts with the verb 取 and then lists seven data domains (1-minute intraday, money flow, margin, convertible bonds, index, valuation history, security universe). This tells the agent the resource area, but it reads as a restatement of the domain enum in the schema. Because the tool spans 7 domains and 20 actions, the purpose is very broad, and the definition never explains how the domain and action work together, nor how the tool differs from siblings such as wmshare_quote or wmshare_history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool instead of the many sibling tools; for example, it does not contrast quote, history, or symbols. It also says nothing about which domain/action pairs are valid; the schema only notes that valid pairs are checked at runtime, and the description does not list them. The agent must work out the usage model from the enums by trial and error.

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