Skip to main content
Glama

wmshare_call

Call catalog functions or friendly APIs for long-tail China, Hong Kong, and US market data queries, with controlled row limits and budget-aware execution.

Instructions

受控通用网关:目录函数和全部 friendly API 的长尾兜底;禁止 _df。

cbond.figures / cbond.article 会写任意路径,网关不开放(改本地 SDK); 单次调用 EC 超过部署上限(WMSHARE_MCP_MAX_EC)会报 ec_budget。

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": {
      "target": "<target>"
    },
    "name": "wmshare_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNotrue 跳过单位规范化,仅诊断用
modeNocatalog=目录函数;api=SDK friendly APIcatalog
unitsNobase 保持 SDK 单位守护;native 保留脚本原值base
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
targetYescatalog function 或 friendly API 的 domain.method
max_rowsNo单次返回的最大行数,硬上限 200
argumentsNo目标函数/method 的公开参数

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does add real value: it discloses that cbond.figures and cbond.article are blocked because they write arbitrary paths, that `_df` is forbidden, and that calls exceeding WMSHARE_MCP_MAX_EC return `ec_budget`. What it omits is significant for a generic dispatcher that can reach arbitrary methods – whether dispatched calls can mutate data, what permissions are needed, and whether calls are idempotent.

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?

The purpose is front-loaded in the first clause and the exclusion/limit notes follow compactly; nothing is padded. The cost is density – `_df`, `ec_budget`, and `WMSHARE_MCP_MAX_EC` appear as unexplained jargon within two short lines.

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?

An output schema exists, so return values need no explanation, and 8 parameters are fully documented in the schema. The description supplies the routing rules and error modes an agent needs. The remaining gap is discovery: it never says how to find a valid catalog function or friendly API name to pass as `target`, which matters for a universal gateway.

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 every parameter already carries its own description and enum values, making 3 the baseline. The description adds essentially nothing about mode, units, market, output, max_rows, or arguments – its only schema-adjacent contribution is the prohibition on `_df` and the blocked functions, which constrains valid `target` values. Useful but minimal.

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 role: a controlled universal gateway that dispatches to catalog functions or SDK friendly APIs, acting as the long-tail fallback. That verb/resource framing is clear and distinguishes it from the many single-purpose siblings (wmshare_quote, wmshare_dividend, etc.) by scope rather than repetition. It stops short of a crisp 'use when no dedicated tool exists' sentence, which keeps it from a 5.

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

Usage Guidelines4/5

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

'长尾兜底' (long-tail fallback) tells the agent this is a secondary route rather than a first choice, and the text explicitly excludes two path-writing functions and the `_df` suffix. That gives both a when-to-use and a when-not. It never names a concrete preferable sibling or explains the catalog vs api decision, but the exclusions are concrete enough to be more than implied guidance.

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