Skip to main content
Glama

Wanmi.AI Domain Tools

域名可注册查询

domain-availability

每次查询一个完整域名,沿用站内服务商路由、只读开关、限流与缓存。available 附本站标准注册价与续费价的展示快照;价格无法完整取得则整次失败、不计次。premium 仅表示溢价,不返回价格;unsupported/restricted/registered 均为明确查询结果。 使用现有 API key 调用,沿用 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": {
      "domain": "<domain>"
    },
    "name": "domain-availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes完整域名,支持 Unicode/IDN;每次只查询一个域名

Output Schema

NameRequiredDescriptionDefault
dataYes
metaNo
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

There are no annotations, so the description must carry the full burden, and it largely does: it discloses provider routing, a read-only switch, rate limiting, caching, billing ('可能收费'), and precise failure semantics (price fetch failure aborts the whole call and is not counted). The remaining gap is that it never states how authoritative or fresh the registry data is.

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 dense and front-loaded: the scope constraint comes first, then result semantics, then billing. Each clause carries information, though the term '站内服务商路由/只读开关' is jargon-heavy and could be plainer for an agent without site context.

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?

For a single-parameter read query with a rich output schema, the description is nearly complete: it covers scope, all status values, failure behavior, and cost. Since an output schema exists, it does not need to explain return structure, and the extra status enumeration is a bonus rather than a gap.

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?

With 100% schema description coverage and a single well-documented 'domain' parameter (Unicode/IDN, pattern, max length), the schema already does the work. The description only restates the one-domain-per-call constraint, adding no new syntax or format detail beyond the schema.

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 clearly states that it checks one fully-qualified domain per call and returns a status (available / premium / unsupported / restricted / registered), which is a specific verb-and-resource statement. It implicitly separates itself from domain-pricing by noting that premium '不返回价格', but it never names a sibling, so an agent must infer which tool to use for price retrieval.

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?

It gives clear usage constraints: one domain per call, use of an existing API key, and possible charges against the API-center quota. However, it offers no explicit when-to-use/when-not-to-use routing against siblings; the closest hint is that 'premium' omits price, which only indirectly points to a pricing tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources