Skip to main content
Glama

PhishDestroy CTI

Check many domains

lookup_domains
Read-onlyIdempotent

Check up to 25 domains in one call: record status per domain (listed, not_found, removed, withdrawn) with the report URL, first-recorded time and confirmed takedown. not_found is not a safety verdict. Unicode names, URLs and defanged [.] input are normalised; invalid entries are listed separately. For evidence call get_domain_report with detail summary.

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": {
      "domains": "<domains>"
    },
    "name": "lookup_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesDomain names (URLs are accepted; only the host is used).

Output Schema

NameRequiredDescriptionDefault
formatYes
limitsYes
schemaNo
invalidYes
resultsYes
generated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low, yet the description adds substantial behavior: the 25-domain batch cap, the enumerated status vocabulary, input normalization (Unicode, URLs, defanged [.]) and the fact that invalid entries come back separately rather than failing the call.

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?

Four sentences, front-loaded with the batch limit and output shape, then the caveat, then the escalation path. No filler, and the parenthetical status list is the most compact way to convey the return vocabulary.

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

Completeness5/5

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

An output schema exists so return values need no elaboration, and the description still covers the limits, normalization, invalid-input handling, interpretation caveat and the alternative tool. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is documented there, so the baseline is 3. The description adds meaning beyond the schema by explaining that URLs are reduced to their host and that Unicode and defanged forms are normalized before lookup.

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 ('Check up to 25 domains in one call') plus the batch ceiling and the exact per-domain outcomes returned (listed, not_found, removed, withdrawn). It also distinguishes itself from the named sibling get_domain_report, so an agent can separate the two without reading 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 Guidelines5/5

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

Gives an explicit routing rule: use this for bulk status checks, and 'for evidence call get_domain_report with detail summary'. It also warns that not_found is not a safety verdict, which prevents a specific foreseeable misuse of the result.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources