Skip to main content
Glama

wmshare_symbols

Resolve company names, pinyin, aliases, or security codes into SDK ticker symbols across CN, HK, and US markets.

Instructions

把公司名、拼音、别名或代码解析为 SDK 标的代码。

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_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden and delivers little: it does not say whether ambiguity produces multiple candidate symbols, whether matching is fuzzy or exact, what happens when nothing matches, or that the market defaults to the server configuration. The only behavioral signal is the implicit mapping from free text to a code.

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?

It is a single front-loaded sentence with no wasted words, and the accepted input types are stated up front. It is arguably too terse for a five-parameter resolution tool, but nothing in it is redundant.

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

Completeness5/5

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

The tool's complexity is moderate and the return shape is covered by the output schema, so the description need not explain results. What is missing is routing guidance and ambiguity-handling behavior, both of which matter for an agent choosing among nineteen siblings, though the core contract is covered.

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 every parameter including limit, market, output, and max_rows is already documented in the schema. The description only echoes the accepted query forms, which are already in the query parameter's description, and adds no syntax or format detail beyond it. Baseline 3 is appropriate.

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 a specific output resource ('SDK 标的代码'), plus the accepted input kinds (company name, pinyin, alias, code). That is enough to distinguish it from data-retrieval siblings like wmshare_quote or wmshare_statement, though it never names a sibling explicitly.

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?

There is no when-to-use guidance: nothing says this should be called first when you only have a name and then feed the result into wmshare_quote, nor does it say when to prefer wmshare_search instead. The use case is inferable from the verb, but no conditions, prerequisites, or exclusions are stated.

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