Skip to main content
Glama

passive_subdomains

Aggregates passive subdomains for a target domain from multiple public sources, deduplicates results, and reports per-source counts and errors.

Instructions

Aggregate passive subdomains from crt.sh, HackerTarget, RapidDNS and OTX.

deep=False skips crt.sh for a fast result. Deduplicates and filters to the target domain, returning per-source counts and errors.

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

Input Schema

NameRequiredDescriptionDefault
deepNo
limitNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/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 disclose meaningful behavior: results are deduplicated, filtered to the target domain, and per-source counts plus per-source errors are returned, which signals partial-failure tolerance. It omits any mention of upstream rate limits, timeouts, or whether the call is network-heavy.

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 short sentences with zero filler; the source list and the deep=False trade-off are both front-loaded and each clause earns its place.

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?

The description covers source set, dedup/filter behavior, and response shape (per-source counts and errors), which is reasonable for a tool with no output schema and no annotations. It falls short on the unexplained 'limit' parameter and on expected latency or upstream rate-limit behavior for a four-source aggregator.

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 explain all three parameters. It explains 'deep' well (skips crt.sh) and 'domain' implicitly as the target, but 'limit' is never mentioned at all — an agent cannot tell whether it caps results globally, per source, or per query.

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?

States a specific verb ('Aggregate') and resource ('passive subdomains') and names the four upstream sources, which implicitly distinguishes it from the single-source sibling crtsh_subdomains. It never explicitly names that sibling, so the differentiation is inferential rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is the conditional 'deep=False skips crt.sh for a fast result', which implies a speed/thoroughness trade-off. There is no statement of when to prefer this aggregator over crtsh_subdomains or the discovery siblings, and no exclusions or prerequisites.

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