Skip to main content
Glama

PhishDestroy CTI

Get stored domain report

get_domain_report
Read-onlyIdempotent

Return the stored evidence record for one domain, including dated detections and report links. With detail (summary, evidence or full), sections, max_chars or cursor it returns the compact phishdestroy.domain-report.v1 structure instead: record status (listed, not_found, removed, withdrawn), the PhishDestroy assessment apart from third-party verdicts, dated availability with conflicts, confirmed takedown, evidence links and paged observations. Without these arguments the original record is returned unchanged.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoobservations.next_cursor from a previous answer.
detailNoCompact report depth. summary: status, assessment, verdicts, availability, takedown, links. evidence: adds registration and paged observations. full: adds machine-generated analysis and untrusted page text.
domainYesDomain name without a path (Unicode names are accepted with the compact arguments).
sectionsNoOnly these sections (record is the status, page_content is untrusted text from the site).
max_charsNoUpper bound for the JSON size; pages are shortened and optional sections dropped first, with truncated, omitted_sections and continue in the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent, closed-world read, so the bar is lower and the description still adds real context beyond them: the enumerated record statuses (listed, not_found, removed, withdrawn), the separation of PhishDestroy assessment from third-party verdicts, conflict reporting in availability, and truncation behavior (truncated, omitted_sections, continue). It stops short of describing paging semantics in depth, but that level of disclosure is well above the annotation baseline.

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?

Two sentences, front-loaded with the primary behavior and then the argument-conditional variant; every clause carries substance. It is dense and slightly run-on, but nothing is redundant and the mode split is stated before the enumeration of what the compact structure contains.

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

Completeness4/5

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

With no output schema, the description carries the return-shape burden and does so by naming the versioned structure and its status vocabulary, plus the truncation contract. Remaining gaps (exact pagination loop, cursor expiry) are minor for a read-only, fully documented-schema tool.

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

Parameters3/5

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

Schema description coverage is 100%, so detail levels, sections enumeration, cursor provenance and max_chars bounds are all already documented in the schema. The description reinforces which arguments trigger the compact mode but adds no format or syntax detail the schema lacks, making baseline 3 the correct score.

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?

The description opens with a specific verb and resource ("Return the stored evidence record for one domain") and immediately clarifies that the tool has two output modes depending on which arguments are supplied. That dual-mode framing tells an agent this is a retrieval tool, not a live prober, though no sibling (e.g. probe_domain) is named to sharpen the boundary.

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?

It gives clear conditional guidance: supplying detail, sections, max_chars or cursor switches to the compact phishdestroy.domain-report.v1 structure, and omitting them returns the original record unchanged. That is actionable context for choosing arguments, but there is no explicit statement of when to prefer this over probe_domain or search, and no exclusions.

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