Skip to main content
Glama

crtsh_subdomains

Enumerate subdomains passively from certificate transparency logs without an API key, falling back to Cert Spotter when crt.sh is overloaded.

Instructions

Enumerate subdomains from certificate transparency logs (crt.sh), passive.

Free, no API key. Falls back to Cert Spotter when crt.sh is overloaded. Can be slow for large domains; subdomain_enum is the active alternative.

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

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?

No annotations are supplied, so the description carries the full burden and does most of the work: it discloses passivity (no direct host contact), that no auth/API key is needed, that upstream overload triggers an automatic fallback to a different provider (Cert Spotter), and that latency can degrade on large domains. It omits what the results look like (format, dedup, whether root domain is included) and how the internal fallback affects result provenance.

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?

Three short sentences, no filler, and the essential fact (what it enumerates and from where, passively) is front-loaded before the operational caveats. Each sentence adds distinct value: source, cost/auth, and the alternative.

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?

There are no annotations and no output schema, so the description must cover both behavior and returns, and it covers behavior well. But for a 2-parameter tool with 0% schema coverage, leaving `limit` and the `domain` input format completely unexplained is a real gap an agent will hit on first invocation.

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 neither parameter is documented anywhere. The description never mentions the required `domain` (bare domain vs URL vs wildcard is left ambiguous) nor the `limit` parameter that defaults to 2000 — an agent has no idea what limit caps or how to raise it for large targets, despite the description itself warning that large domains are slow.

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 ("Enumerate subdomains from certificate transparency logs (crt.sh)") plus a defining scope qualifier ("passive"). It also names the sibling it is not, subdomain_enum (the active alternative), so an agent can discriminate the two 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?

Clear routing context: passive source, free/no API key, automatic fallback to Cert Spotter when crt.sh is overloaded, and slow on large domains, with subdomain_enum flagged as the active alternative. The passive-vs-active tradeoff is implied rather than stated as an explicit rule ("use this when you want no-noise passive data; use subdomain_enum when you need coverage"), which keeps it just under a 5.

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