Skip to main content
Glama

wmshare_batch

Batch-invoke catalog functions across a symbol list, pass shared params, and return request counts, errors, and 429 resume positions for retrying.

Instructions

批量调用目录函数;支持 params,返回请求数、错误和 429 续跑位置。

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

Input Schema

NameRequiredDescriptionDefault
rawNotrue 跳过单位规范化,仅诊断用
unitsNobase 保持 SDK 单位守护;native 保留脚本原值base
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
paramsNo透传给 batch_iter 的目录函数参数
symbolsYes同市场标的列表;不要混合 cn/hk/us
functionYes目录函数名;先用 search/contract 确认
max_rowsNo单次返回的最大行数,硬上限 200
batch_sizeNo每批标的数
on_batch_errorNo批级错误策略;skip 仍会记录失败批skip

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 full burden falls on the description. It does add real behavioral information by naming the return payload (request count, errors, 429 resume position), but it omits how resumption actually works, whether partial results are returned, and what rate limits trigger the 429.

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?

One compact sentence leads with the core action and then lists the outputs, with no filler. It is dense but front-loaded, and every clause carries information.

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?

With ten parameters, an output schema, and full schema coverage, the description only needs to cover the selection model and the behavior that the structured fields do not capture. It explains the returned fields but not when to call the tool or how to use the 429 continuation position.

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%, so the schema already documents all ten parameters in detail. '支持 params' adds nothing beyond the schema; the description's stronger value comes from the return-value clause, not from describing its inputs.

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 uses a specific verb and resource: 'batch-invoke catalog functions' (批量调用目录函数). That immediately separates it from single-call siblings such as wmshare_call, although no sibling is named and 'catalog function' is left for the agent to resolve from the `function` parameter.

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?

Bulk usage is only implied by '批量' and by the `symbols` requirement. The description never states when to prefer this over wmshare_call, that all symbols must share one market, or when batching is not worthwhile; those rules appear only in the schema.

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