Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

subdomain_enum

Discovers subdomains for a target domain using passive or active enumeration methods, including brute force, to map an attack surface during security reconnaissance.

Instructions

Discover subdomains using multiple methods (amass-style enumeration)

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

Input Schema

NameRequiredDescriptionDefault
domainYesTarget domain
methodNoMethod: 'passive' (safe) or 'active' (includes brute force)passive

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 provided, so the description carries the full behavioral burden and does not meet it. It never mentions authorization requirements, aggressiveness or rate implications of 'active' brute-force discovery, or what kind of results come back — all critical for a security enumeration tool.

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 short sentence with no padding and the key concept front-loaded. It is efficient, though 'amass-style enumeration' is parenthetical filler that does not add actionable meaning.

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?

For a two-parameter offensive-security tool with no annotations and no output schema, the definition is too thin. It omits what the tool returns, whether active mode is intrusive or requires authorization, and how this differs from the similarly named dns_enum sibling.

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 are already documented in the schema, including the 'passive' vs 'active (brute force)' distinction. The description's 'multiple methods' adds only a faint pointer to the method parameter, so the baseline 3 is appropriate.

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 specific verb and resource ('Discover subdomains'), which is clear enough to distinguish it from DNS/IP-oriented siblings like dig_dns or whois_lookup. However, it offers no explicit contrast with dns_enum, and 'amass-style enumeration' merely restates the verb rather than adding differentiating detail.

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, no prerequisites, and no named alternative among the 16 siblings. The phrase 'using multiple methods' hints that a method exists but never explains when to prefer this tool over dns_enum or host_discovery.

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