Skip to main content
Glama

Check a domain or IP against the compromised feed

check_compromised
Read-onlyIdempotent

Checks if a domain, hostname or IP address appears in a compromised feed for malware, phishing or abuse, returning first and last seen dates, block reason and registrar.

Instructions

Is a domain name or IP address in the NetAPI compromised feed (malware, phishing, abuse)? Returns whether it was seen in the last 24 hours (listed_now), ever (listed_ever), first/last seen dates, the block reason and the registrar. Subdomains are matched against their parent domains too. Free, no account needed.

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": {
      "value": "<value>"
    },
    "name": "check_compromised"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesDomain name (example.com, also a URL or hostname) or an IPv4 / IPv6 address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: the subdomain-to-parent matching rule, the return semantics (listed_now vs listed_ever, first/last seen, block reason, registrar), and the no-account/no-cost access condition.

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 as a direct question, followed by return fields, the subdomain rule, and the access condition. Four short sentences with essentially no filler, though the trailing 'Free, no account needed' is the least essential line.

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?

There is no output schema, and the description compensates by enumerating the key return fields and the matching behavior. Combined with the 100%-covered single parameter and the safety annotations, an agent has everything needed to invoke it correctly.

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% and the single parameter is fully documented in the schema (domain, URL, hostname, IPv4/IPv6). The description adds no format or syntax detail beyond what the schema already provides, so the baseline of 3 applies.

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 gives a specific verb+resource: checking a domain/IP against the 'NetAPI compromised feed (malware, phishing, abuse)'. The feed name makes it distinguishable from generic siblings like lookup_domain or lookup_ip, but it never explicitly contrasts itself with those tools, so it falls just short of the top score.

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?

Usage context is implied (use this to check whether an indicator is compromised) and it notes 'Free, no account needed', but there is no explicit when-to-use vs when-not, and no mention of how it relates to lookup_domain/lookup_ip or other reputation siblings.

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