Skip to main content
Glama

Wanmi.AI Domain Tools

DNS 查询

dns-lookup

沿用站内 DNS 服务,type 可选 A/AAAA/CNAME/MX/TXT/NS/SOA/CAA;省略返回全部八类,指定时仅返回该类。只访问公网;NXDOMAIN/无记录是 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": "dns-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo记录类型;省略时返回全部八类,指定时仅返回该类
domainYes

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?

With no annotations provided, the description carries the full burden and does well: it discloses public-only access, that empty results are success, that a partial type failure fails the whole call and is not counted ('不计次'), and that calls consume the existing API key quota and may be billed. Remaining gaps are rate limits and the exact error payload shape, but the billing and failure semantics are unusually well covered.

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?

Two dense sentences, front-loaded with type/default behavior and followed by failure and billing semantics; nothing is padding. The second sentence is a compressed run-on combining API-key, quota, and billing facts that could read more cleanly, but no content is wasted.

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 structure need not be described, and the description covers the non-obvious behaviors (empty-as-success, whole-call failure, billing). What is missing is the domain input's format expectations and any rate-limit framing, which matters for an agent constructing the request.

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 coverage is 50%: 'type' already has an enum plus a description mirroring the prose, so the description adds nothing new there beyond confirming the default-all behavior. 'domain' is undocumented in both schema and description — no format, punycode/IDN, or trailing-dot guidance — which is a meaningful gap 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 uses a concrete verb+resource (DNS record lookup) and states scope explicitly: '只访问公网' and the eight record types. It never names a sibling such as whois or domain-availability, so an agent must infer the boundary between this and related domain tools, which keeps it below a 5.

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 explains the omit-vs-specify behavior for 'type' and notes that NXDOMAIN/no-record is a successful empty result rather than a failure, which is real usage guidance. It gives no when-to-use vs when-not guidance relative to the domain-related siblings, so the guidance is implied rather than explicit.

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