Skip to main content
Glama

wmshare_search

Search an offline catalog for functions, metric codes, friendly APIs, and market symbols by name or code to resolve the right identifier before querying.

Instructions

离线搜索函数、指标码、friendly API 和标的;任何名字/代码先查这里。

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": {
      "query": "<query>"
    },
    "name": "wmshare_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo检索类型;api 搜索 154 个 SDK friendly APIall
limitNo最多返回条数
queryYes中文关键词、英文函数名、指标码、标的名或代码
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • changedInput schema / properties / kind / description
      Previous value: -"检索类型;api 搜索 139 个 SDK friendly API"New value: +"检索类型;api 搜索 154 个 SDK friendly API"
  2. Changed1 schema field changedv1.20.4
    • changedInput schema / properties / kind / description
      Previous value: -"检索类型;api 搜索 136 个 SDK friendly API"New value: +"检索类型;api 搜索 139 个 SDK friendly API"
  3. First observedv0.1.0

TDQS

A3.8/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 that the search is offline (local index rather than live service), which is useful behavioral context beyond the schema. It omits whether the operation is purely read-only, index freshness, and any paging/rate behavior; the output schema covers the response shape.

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 semicolon-joined sentence, with the resource scope front-loaded and the routing rule second. Nothing is redundant and nothing an agent needs is buried.

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?

With six parameters, an output schema and full schema-level documentation, the definition is nearly complete: the gap the description should close is the relationship to sibling lookup tools, which it addresses only generically. Index staleness or offline-vs-live caveats would round it out.

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 query, kind, limit, market, output and max_rows are all already documented in the schema. The description only echoes that kinds and codes can both be searched, adding little beyond that baseline.

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?

States a concrete verb (search, 搜索) over four named resource types — functions, metric codes, friendly APIs and symbols — and adds the 'offline' qualifier, so the agent knows exactly what it returns. The only gap is that it never names a sibling such as wmshare_symbols or wmshare_metrics to say how it differs.

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?

'任何名字/代码先查这里' is an explicit routing rule: resolve any name or code through this tool before acting. That is real when-to-use guidance. It stops short of exclusions, e.g. when a direct sibling like wmshare_quote or wmshare_metrics is preferable instead.

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