Skip to main content
Glama

recon_domain

Run parallel passive checks on a domain: DNS, RDAP whois, TLS cert, crt.sh subdomains, headers, tech, and robots; get a compact summary plus full results.

Instructions

One-shot domain recon: DNS, RDAP whois, TLS cert, crt.sh subdomains, headers, tech, robots.

Runs 8 passive checks in parallel and returns a compact summary plus the full results. Start here for a new domain, then drill down with the specific tools.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does real work: it discloses that the 8 checks run in parallel, that they are 'passive' (implying no active probing of the target), and that output is a compact summary plus full results. It omits auth requirements, rate limits, and typical runtime, which keeps it below the top score.

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?

One dense, front-loaded sentence lists the checks, and the second sentence delivers the behavioral facts and the routing advice. No filler, and the most decision-relevant information (what it covers and when to pick it) comes first.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description covers what is run, how it is run, and roughly what is returned, which is enough to call it correctly. The remaining gap is input format for 'domain', which matters for a 0%-coverage schema.

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?

The single 'domain' parameter has 0% schema description coverage, so the description must compensate, but it never states the expected format (apex domain vs. subdomain vs. URL, and whether IPs are accepted). The reader can infer an apex domain from 'for a new domain' but nothing is explicit.

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 ('One-shot domain recon') and then enumerates the exact checks performed (DNS, RDAP whois, TLS cert, crt.sh subdomains, headers, tech, robots). This is clearly distinguishable from narrower siblings like domain_whois or recon_deep because it is scoped as the combined entry point.

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?

'Start here for a new domain, then drill down with the specific tools' gives an explicit when-to-use rule and an ordering versus alternatives. It stops short of naming which specific tool to reach for after a given finding, so it is clear context rather than a full when/when-not map.

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