Skip to main content
Glama
Sign In
Whoisfreaks

Whoisfreaks

by WhoisFreaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Bulk DNS lookup

bulkDnsLookup
Read-onlyIdempotent

Resolve DNS records for up to 100 domains or PTR records for up to 100 IPs in one request, replacing repeated single lookups for batch mail-server checks or log IP naming.

Instructions

Resolve the current DNS records of up to 100 domains, and the PTR records of up to 100 IP addresses, in one request. Use this instead of calling dnsLookup many times, for example to check the mail servers of a list of domains or to name a list of IPs from logs. Provide domainNames, ipAddresses, or both. For one domain or IP use dnsLookup. Lists longer than 100 go in several calls; files of up to 3 million entries are handled by the Bulk Tool in the WhoisFreaks billing dashboard, not by this tool. Costs 1 credit per domain or IP. A large batch can take a few minutes. Returns one entry per domain or IP, with the same record fields as dnsLookup. Behavior: read-only. Makes one request to the WhoisFreaks API using your WhoisFreaks API key (the WHOISFREAKS_API_KEY environment variable, or on the hosted server the key sent with the request) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

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": "bulkDnsLookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRecord types to return: 'all' (the default), one type such as MX, or a comma-separated list such as a,mx,ns. Supported: A, AAAA, TXT, NS, MX, SOA, SPF.
formatNoResponse format. Default: json
cnameDepthNoHow many CNAME hops to follow before collecting records, 0 to 4. Default: 0
domainNamesNoDomain names to resolve, at most 100. Example: ["whoisfreaks.com", "jfreaks.com"]
ipAddressesNoIP addresses for reverse (PTR) lookups, at most 100. Example: ["1.1.1.1", "8.8.8.8"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, yet the description still adds real context beyond them: credit cost per domain/IP, multi-minute latency for large batches, API-key sourcing (WHOISFREAKS_API_KEY or request-supplied key), and enumerated failure modes with HTTP codes (401/403/404/429) returned as a short message instead of data. The only minor gap is it does not say whether partial successes are returned when some entries fail.

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?

Front-loaded with purpose, then alternatives, then cost/behavior, then returns — a sensible ordering with no filler sentences. It runs long, and the parenthetical HTTP-code enumeration is denser than an agent strictly needs, but every sentence carries actionable information.

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

Completeness5/5

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

For a 5-parameter batch tool with no output schema, the description covers cost, latency, auth, error behavior, and return shape ('one entry per domain or IP, with the same record fields as dnsLookup'). An agent has everything needed to decide to call it and to interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the schema carries record types, format, cnameDepth and the 100-item caps. The description still adds the non-obvious combination rule ('Provide domainNames, ipAddresses, or both'), which the schema does not express since no parameter is required and there is no anyOf constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with explicit scope: 'Resolve the current DNS records of up to 100 domains, and the PTR records of up to 100 IP addresses, in one request.' It also names the sibling it replaces (dnsLookup) and the single-item alternative, so the agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('instead of calling dnsLookup many times'), concrete example scenarios (mail servers of a list of domains, naming IPs from logs), a when-not ('For one domain or IP use dnsLookup'), and boundary routing for lists over 100 and for multi-million-entry files that belong to the dashboard Bulk Tool.

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

Deploy Server

Other Tools