Skip to main content
Glama

wmshare_screen

Screen individual stocks or the whole market by custom conditions and return breadth summaries, industry distributions, top movers, or industry members.

Instructions

取单票筛选、全市场条件选股、宽度、行业分布、涨跌榜或行业成分。

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

Input Schema

NameRequiredDescriptionDefault
idxNo宽度/涨跌榜/条件选股的服务端索引键
descNotop_movers / query 的 order 是否降序
testNoaction=boolean 时的筛选器
limitNo返回条数上限
whereNoaction=query 的条件表达式($码 用 && / || / !,比率=小数)
actionYes筛选动作;boolean 需要 symbol/test,query 需要 where
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
paramsNo筛选器额外参数,如 min_chg/min_ratio;query 可带 order/offset/fields
symbolNo单票筛选用的标的代码
industryNoindustry_members 需要的行业 id
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about permissions, cost, rate limits, whether results are cached/sampled, or how the three output modes differ in practice. It merely names the resource areas already listed in the action enum.

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?

A single dense sentence that front-loads the capability list with no filler. It is compact, though the comma-separated enumeration reads more like a label set than a structured explanation.

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?

For an 11-parameter, 8-action tool with no annotations, the description is thin; it leans on the fully documented schema and the existing output schema. Action-specific requirements (e.g., boolean needs symbol/test, query needs where) are only stated in the schema, not the description, which is acceptable but leaves little margin.

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 (idx, where, test, symbol, industry, output, max_rows, params) is already documented in structured form. The description adds no syntax examples, units, or cross-parameter constraints (e.g., which params each action requires), so it stays at the 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?

The description enumerates the six capability areas the tool covers (single-symbol screening, market-wide conditional screening, breadth, industry distribution, top movers, industry constituents), which maps cleanly onto the action enum. An agent can tell it is a multi-action screening tool, though nothing distinguishes it from siblings like wmshare_market or wmshare_symbols.

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: no indication of which action to pick for a given question, no prerequisites, and no mention of alternatives among the many sibling tools. The agent must infer routing entirely from the action enum descriptions in the schema.

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