Skip to main content
Glama

wmshare_segments

Retrieve a company’s operating segments by business, product, region, income, coverage, period, or four-dimensional snapshot, with market, source, and output controls.

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限
actionYes经营分部动作
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
sourceNo分部数据源:clean 规范视图或 raw 原始视图clean
symbolNo标的代码;所有 action 都需要
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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, and it discloses almost nothing: not that this is a read-only retrieval, not what the clean vs raw source distinction implies, not how limit, max_rows (hard cap 200) and the sample/count/summary output modes interact, and not what happens when market is omitted. It does at least convey the broad scope of retrieval across segment dimensions, which keeps it above a 1.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is structurally clean. But the brevity comes from under-specification rather than economy — the enumeration duplicates the enum instead of spending those words on scope, defaults, or return behavior.

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

Completeness2/5

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

For a 7-parameter tool spanning 7 distinct actions with two data sources and three output modes, the description is far too thin; an output schema exists so return values need not be explained, but action semantics and parameter interplay should be. An agent can guess, but cannot confirm from the text what each action yields or how market/source defaults behave.

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%, including descriptions for action, market, output, source, symbol, limit and max_rows, so the schema already does the heavy lifting. The description adds no new meaning beyond echoing the action values and omits any explanation of how the parameters combine. Baseline 3 applies when structured fields fully document the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb (取) and a resource (经营分部) and lists the dimensions available, so the general domain is clear. However, the list ('业务、产品、区域、收入、覆盖期、期间或四维快照') is a near-verbatim restatement of the action enum in the schema rather than an explanation of what the tool actually returns. It also does nothing to distinguish this tool from siblings such as wmshare_company or wmshare_metrics that presumably also touch company-level financial data.

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 mention of when to choose another sibling tool, and no stated prerequisites (e.g. that a symbol is required for every action). The only routing information an agent can infer is from the action names themselves, not from the description.

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