Skip to main content
Glama

PhishDestroy CTI

Search published reports

search
Read-onlyIdempotent

Search published PhishDestroy domain reports by a domain (exact; URLs and defanged input accepted), the start of a domain name (3+ characters) or an impersonated brand as stored (e.g. Coinbase, MetaMask). Returns up to 20 results (id = domain, title with the first-recorded date, url = report page), newest brand matches first. Read one with fetch. An empty result is not a safety verdict.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesDomain, start of a domain name, or brand name.

Output Schema

NameRequiredDescriptionDefault
noteNo
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: a hard cap of 20 results, newest-brand-first ordering, and the important caveat that an empty result is not a safety verdict. Some of the return-shape detail (id, title, url) overlaps with the existing output schema, which keeps it from a 5.

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?

A single dense passage with the core action and input modes front-loaded, followed by result shape, follow-up routing, and the caveat. Every clause carries operational information; nothing is padding.

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?

For a one-parameter, idempotent read tool with a full output schema and complete annotation coverage, the description supplies everything an agent needs: valid inputs, result cap, ordering, follow-up tool, and the interpretation caveat for empty results.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds genuine meaning beyond the single schema line: exact-domain matching, acceptance of URLs and defanged input, the 3+ character rule for prefix search, and that brand names must be supplied as stored. This disambiguates three distinct query modes that the schema alone leaves ambiguous.

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 ('Search published PhishDestroy domain reports') and immediately scopes the three accepted query modes, so an agent knows exactly what this tool retrieves. It also differentiates itself from the sibling 'fetch' by naming it as the follow-up for reading a single report.

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?

The description clearly routes the agent: search here, then 'Read one with fetch', and it explains which input forms are valid (exact domain, domain prefix, brand). It does not explicitly rule out alternatives like get_domain_report or lookup_domains, so the when-not guidance is inferential rather than stated.

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