Skip to main content
Glama

wmshare_status

Check server version, markets, credentials, catalog, capability coverage, and setup guidance without credentials. Use it to verify configuration and discover market data features.

Instructions

查看版本、市场、凭证、目录、能力覆盖和配置指引(零凭证可用)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wmshare_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/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 disclosure burden. It does contribute one valuable behavioral fact — the tool works with zero credentials — but says nothing about side effects, whether it is strictly read-only, latency or rate limits, or what the response contains beyond a topic list. For an unannotated tool, that leaves most behavioral questions unanswered.

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 with the verb front-loaded and no filler; the parenthetical credential note is well placed. The comma-separated topic list is efficient, though it reads as an inventory rather than organizing the information by importance.

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 an output schema present, 100% parameter coverage, and zero required parameters, the description only needs to convey scope and the no-credential property, which it does. The remaining gap is the unannotated behavioral profile (read-only status, side effects), which matters less for a status/introspection endpoint than it would for a mutation tool.

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 both parameters (output enum and max_rows with its 200 cap) are already fully documented in the schema. The description adds no additional semantics about how 'sample'/'count'/'summary' affect what the agent receives, nor how max_rows interacts with the summary mode. Baseline 3 is appropriate when the schema does all the work.

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 names a specific verb (查看/view) and an explicit set of resources: version, markets, credentials, catalog, capability coverage, and configuration guidance. That enumeration clearly distinguishes it as a meta/status-introspection tool rather than a data-query sibling. It stops short of naming any sibling or stating the contrast explicitly, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical '(零凭证可用)' signals this is the thing to call before credentials are configured, which is a genuine onboarding hint. There is no explicit 'call this first' instruction, no statement of when not to use it, and no pointer to alternatives for the actual data lookups. Adequate but inferential.

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