Skip to main content
Glama

subdomain_takeover_check

Detect subdomain takeover risks by resolving CNAMEs and matching unclaimed provider fingerprints; identifies high-confidence vulnerabilities and potential dangling records.

Instructions

Check subdomains for dangling CNAMEs to known takeover-prone providers.

Enumerates subdomains (or accepts a comma/newline-separated host list), resolves CNAMEs, and fetches each host to match provider-specific unclaimed fingerprints. High confidence requires a matching fingerprint; a matching CNAME alone is potential.

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

Input Schema

NameRequiredDescriptionDefault
deepNo
limitNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses the pipeline (enumerate, resolve CNAMEs, fetch each host, match provider fingerprints) and the confidence model ('High confidence requires a matching fingerprint; a matching CNAME alone is potential'). What it omits is operational behavior — how many network requests the fetches entail, whether any limit/rate concerns exist, and what the result looks like. The confidence-tier explanation is genuinely useful context that annotations would not have provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then input modes, then the confidence semantics — a logical order with no filler sentences. Slightly dense line-broken phrasing, but every clause carries information; nothing should be cut.

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 moderately complex network-checking tool with no annotations and no output schema, the description covers the mechanism and confidence interpretation well. The remaining gaps are the two undocumented parameters and any indication of result shape or cost/runtime, which matter for an agent deciding whether to invoke this or how to interpret output.

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. It partly does for 'domain', explaining that a comma/newline-separated host list is accepted instead of a single domain. But 'deep' and 'limit' are completely undocumented in both schema and description — the agent has no idea what deep mode changes or whether limit caps enumerated subdomains or fetches.

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 and resource: 'Check subdomains for dangling CNAMEs to known takeover-prone providers.' The agent can distinguish this from breach_check or dnsbl_check without opening the schema. It loses a point only because the phrase 'Enumerates subdomains' overlaps conceptually with the subdomain_enum sibling, and the description never clarifies the boundary between the two.

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?

It conveys the input modes ('enumerates subdomains (or accepts a comma/newline-separated host list)') and the confidence interpretation, so intended usage is implied. However, there is no explicit when-to-use/when-not guidance and no statement about when to prefer subdomain_enum first or when this check is redundant. Usage is inferable, not directed.

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