Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

whois_lookup

Retrieve domain registration details, including registrar and ownership data, to verify domain information and support security investigations.

Instructions

Perform WHOIS lookup for a domain to get registration info

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_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to lookup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no indication of live query vs cache, rate limiting, authentication/proxy needs, behavior for unregistered or private-registrar domains, or the shape of the result. Only the fact that it is a read-style lookup is inferable from 'lookup'.

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?

One front-loaded sentence with no filler or repetition. It is arguably too terse rather than too long, but nothing in it is wasted.

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?

A single-parameter read tool is simple, but with no annotations and no output schema the description should at least sketch what 'registration info' contains and any failure modes. As written it is minimally adequate rather than complete.

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 100% for the single 'domain' parameter, so the schema already documents the input. The description adds no format guidance (e.g., whether a bare domain, URL, or IDN is expected), so baseline 3 applies.

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 (WHOIS lookup) and resource (domain) plus the outcome (registration info). It is distinguishable from DNS-resolution siblings like dig_dns in practice, but the description never says so explicitly.

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?

'to get registration info' implies the use case (registrant/registrar data rather than DNS records), which is the only usage signal. There is no explicit when-to-use or when-not guidance, and no reference to sibling tools such as dig_dns or dns_enum.

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