Wezzet AI Comms

dns_lookup

DNS lookup over Cloudflare DNS: A, AAAA, CNAME, MX, NS, TXT by default. Give an IPv4 address for a reverse (PTR) lookup.

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": {
      "name": "<name>"
    },
    "name": "dns_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Domain name or IPv4 address
`type`	No	Comma separated: A, AAAA, CNAME, MX, NS, TXT, SOA, SRV, CAA, HTTPS, PTR

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral load. It discloses the resolver (Cloudflare) and the default record-type set, but says nothing about response shape, rate limits, failure behavior for NXDOMAIN, or whether queries are cached.

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

Conciseness5/5

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

Two tight sentences with the forward default first and the reverse mode second. Every clause carries information; no filler.

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

Completeness3/5

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

For a two-parameter read tool with no annotations and no output schema, the description covers inputs well but leaves an agent guessing what the result looks like (record list? single value? errors?). Adequate but with a visible 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?

Schema description coverage is 100%, so the baseline is 3. The description adds that omitting 'type' yields six default record types and that supplying an IPv4 address switches to PTR, which goes slightly beyond the schema, but it does not explain syntax such as comma-separated multi-type requests beyond what the schema already says.

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?

States a specific verb and resource ('DNS lookup over Cloudflare DNS') and names the record types returned, plus a separate reverse-lookup mode. None of the sibling tools are DNS-related, so no discrimination is required, but the scope of what is queried is clear.

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

Usage Guidelines4/5

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

Explains the two usage modes: default forward lookups covering six record types, and reverse lookups triggered by supplying an IPv4 address. It gives clear context for choosing a mode but names no exclusions or prerequisites.

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

All Wezzet AI Comms tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?