Skip to main content
Glama

Wanmi.AI Domain Tools

WHOIS 查询

whois

公开 RDAP/WHOIS 注册信息,公开源失败时使用既有兜底。联系人沿用站内隐私规则;不返回上游服务商标识和原文。无公开记录是成功的 empty 结果。 使用现有 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": "whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault
dataYes
metaNo
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the fallback path, that contact data is filtered by in-site privacy rules, that upstream provider identifiers and raw text are stripped, that a missing record is a successful empty result, and that the call consumes API-center quota and may incur charges. Only rate limits and failure/error modes remain unstated.

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?

Four short sentences, front-loaded with purpose followed by privacy, empty-result, and billing caveats; almost nothing is redundant. Phrasing is compact but readable.

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?

An output schema exists, so return shape need not be explained, and the description covers privacy filtering, empty-result semantics, and billing—the non-obvious facts for this tool. The main gap is input format for the domain argument, which is left entirely to the caller's guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description must compensate, but it never mentions 'domain' at all. It does not say whether a bare registrable domain is expected, whether subdomains/URLs are rejected, or whether IDN/punycode input is accepted (relevant given the idn-convert sibling).

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+resource: exposing public RDAP/WHOIS registration information. It is clearly distinguishable from siblings like dns-lookup or domain-availability in that it returns registration/ownership records, though it never names an alternative 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 behavioral context (fallback when public sources fail, empty result treated as success) but no guidance on when to choose this over domain-availability, dns-lookup, or website-check. An agent must infer the selection criteria from sibling names alone.

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