Skip to main content
Glama

subdomain_enum

Brute-forces subdomains of a domain using built-in or custom wordlists, optional permutations, and wildcard-DNS filtering to remove false positives.

Instructions

Brute-force subdomains of a domain using a built-in wordlist (or a custom one).

wordlist may be a file path, a comma/space separated list, or empty for the built-in 1280+ entry list. permutations=True also probes common derived labels (e.g. api-dev, api2, dev-api). Performs wildcard-DNS detection and filters wildcard matches so results are not polluted. Passive alternative: crtsh_subdomains.

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
domainYes
timeoutNo
wordlistNo
concurrencyNo
permutationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: wildcard-DNS detection and filtering of wildcard matches, plus what permutations adds. It omits that this tool generates many DNS queries against the target (noise/detectability) and says nothing about the empty-wordlist fallback cost or result format.

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?

Four short sentences, front-loaded with the core action, with parameter names code-formatted for scanability and a concrete permutation example. No filler or restated title.

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?

With no annotations and no output schema, the description is the sole carrier of behavior, and it never states what a result looks like (bare hostnames? resolved IPs? subdomain-plus-status?). For an enumeration tool whose output format drives downstream use, that is a real gap, though the scoping and wildcard-filtering details cover the most likely failure mode.

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 0%, so the description must compensate for 5 parameters. It fully explains `wordlist` (file path, comma/space list, empty → built-in 1280+ entries) and `permutations`, but leaves `timeout` (units unclear, default 3) and `concurrency` (default 80) entirely uninterpreted, and only implicitly covers `domain`.

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?

Opens with a specific verb+resource ('Brute-force subdomains of a domain') and immediately scopes the mechanism (built-in or custom wordlist). It also names the sibling it is not — 'Passive alternative: crtsh_subdomains' — so an agent can distinguish active brute-force from passive certificate-transparency lookup without opening either schema.

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?

The 'Passive alternative: crtsh_subdomains' line gives an explicit alternative and implies the selection criterion (active brute-force vs passive). It lacks a positive 'use this when you need X' statement and gives no guidance on cost/time implications of running brute-force vs the passive sibling.

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