Skip to main content
Glama

recon_deep

Run parallel passive reconnaissance to uncover subdomains, archived URLs, API surfaces, email security gaps, threat intel, and exposed hosts for exposure analysis.

Instructions

Deep passive recon: subdomains + archives + API surface + email + threat intel.

Runs passive_subdomains, urlscan, Common Crawl, api_discovery, well_known, email_security, threat_reputation and favicon_hash in parallel. Slower than recon_domain but aimed at forgotten endpoints, dangling hosts and exposure.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses passivity (no active probing), that eight named sub-collectors run in parallel, and that the call is comparatively slow. It does not disclose any cost/rate-limit implications of fanning out to eight sources, nor what happens when a collector fails or returns nothing.

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?

Two tightly packed sentences with zero filler. The purpose and coverage list is front-loaded, and the comparative note about recon_domain and the exposure target follows immediately, so the agent gets the decision-relevant facts first.

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?

For a fan-out aggregator with no annotations and no output schema, the description adequately explains what is collected and how, but leaves two gaps an agent must guess at: the semantics of 'limit' and the shape/size of the aggregated response across eight sources. The behavioral picture is solid; the calling contract is not fully covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 and it does not: neither 'domain' nor 'limit' is mentioned. 'limit' in particular is ambiguous — it is unclear whether it caps subdomains, results per source, or total results across the eight parallel collectors — and the description offers no clarification.

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 ('Deep passive recon') and enumerates the exact data classes it collects: subdomains, archives, API surface, email, threat intel. It also names the sibling it differs from ('Slower than recon_domain') and the goal that differentiates it (forgotten endpoints, dangling hosts, exposure), so an agent can distinguish it without opening any 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?

Gives a clear selection signal: it is slower than recon_domain and is aimed at forgotten endpoints, dangling hosts and exposure, which implies using it when breadth/exposure hunting matters more than speed. It stops short of an explicit 'use recon_domain instead when X' exclusion, and says nothing about cost, rate limits, or when the extra time is not warranted.

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