Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

dns_enum

Enumerate DNS records and discover subdomains for a target domain using a wordlist, helping map exposed infrastructure during security assessments.

Instructions

Perform DNS enumeration to find subdomains and DNS records

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

Input Schema

NameRequiredDescriptionDefault
domainYesTarget domain to enumerate
wordlistNoSubdomain wordlist path/usr/share/wordlists/dnsmap.txt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly drops it. It does not disclose that the wordlist parameter implies an active brute-force sweep that sends many queries, whether it is slow or rate-limited, whether authorization is expected, or how results are aggregated.

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?

A single, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why behavioral detail is missing rather than a sign of well-targeted structure.

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

Completeness2/5

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

This is a network-scanning tool with no annotations and no output schema, and the description leaves the agent without the information needed to call it responsibly or to predict its result set. It should at minimum indicate that the wordlist drives an active subdomain sweep and roughly what the response contains.

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 both parameters, including the wordlist default path, are already documented in the schema. The description names the output categories but adds no detail on wordlist format, custom wordlist behavior, or output syntax beyond what the schema provides, 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?

The description states a concrete verb and resource (DNS enumeration) plus the two artifact types it returns: subdomains and DNS records. It does not differentiate from the close siblings dig_dns and subdomain_enum, which cover overlapping ground, so an agent cannot tell from the description alone which one to pick.

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 no when-to-use guidance at all: no indication of when this is preferable to dig_dns for straight record lookups or subdomain_enum for pure subdomain discovery. The only implicit signal is the wordlist parameter, which suggests brute-force discovery, but the description never says so.

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