Skip to main content
Glama

PhishDestroy CTI

Read a report

fetch
Read-onlyIdempotent

Read one PhishDestroy domain report found with search (id = domain): record status, assessment, third-party verdicts with dates, availability, takedown and evidence links, as text and JSON (phishdestroy.domain-report.v1, 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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of a search result (a domain).

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, enumerating the report's contents (status, assessment, dated third-party verdicts, availability, takedown and evidence links) and the dual text/JSON output with schema version phishdestroy.domain-report.v1. It omits error behavior for an unknown or malformed id, which is the main remaining gap.

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?

The single sentence is front-loaded with the verb and resource, and every clause (provenance, field list, format, schema version) carries information. It is dense and slightly overloaded by the trailing parenthetical, but there is no filler.

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?

For a one-parameter read tool with full annotation coverage and an output schema, the definition supplies what an agent needs: where the id comes from, what the report contains, and the response format. Only failure modes for an invalid id are unaddressed.

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 coverage is 100% and the schema already says the id is "the id of a search result (a domain)." The description only reinforces this with "(id = domain)" and adds the provenance hint that it was obtained via search, which is a marginal gain over the structured field rather than new semantics.

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 ("Read one PhishDestroy domain report") and distinguishes itself from the discovery tool by tying the input to a result "found with search." It does not, however, differentiate itself from the sibling get_domain_report, which by name appears to address the same resource, leaving a residual ambiguity.

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 establishes a clear prerequisite — the id must come from a prior search and equals the domain — which is useful routing context. It gives no explicit when-not guidance and never explains how this differs from the similarly named get_domain_report sibling, so an agent facing both must guess.

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