Skip to main content
Glama

IP-DB IP Reputation

Check IP blacklists

check_blacklists
Read-onlyIdempotent

Check one IP address against every threat-intelligence blocklist IP-DB carries plus live DNSBL/RBL spam blacklists (SpamCop, Barracuda, PSBL, UCEPROTECT, Mailspike and more). Returns which lists carry it and which do not.

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": {
      "ip": "<ip>"
    },
    "name": "check_blacklists"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 or IPv6 address, or a hostname to resolve first (e.g. 185.220.101.1, mail.example.com)

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 readOnlyHint, idempotentHint, and openWorldHint, so safety is covered; the description adds genuinely new context by stating that queries hit live DNSBL/RBL services (external, third-party dependent) and that results report both listings and non-listings. It does not mention latency, rate limits, or caching of the live lookups.

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?

Two tightly packed sentences with the scope front-loaded and provider examples used economically; nothing is redundant or padded.

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 one parameter and no output schema, the description usefully explains the return shape (which lists carry it and which do not), which is what an agent most needs. Only the live-lookup costs/limits are left unstated.

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 already documents IPv4/IPv6/hostname handling with an example, so the schema carries the burden. The description adds only the 'one IP address' constraint (no batch input), which is minor additional meaning. Baseline 3 is appropriate.

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?

States a specific verb and resource: check a single IP against IP-DB's threat-intelligence blocklists plus live DNSBL/RBL lists, naming concrete providers (SpamCop, Barracuda, PSBL, UCEPROTECT, Mailspike). That is far more precise than the title alone, though it never explicitly contrasts with the sibling check_ip, so an agent must infer the split.

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?

Intended usage (reputation/blacklist screening of an IP) is implied by the wording, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as check_ip or domain_whois. Adequate but with a clear guidance gap.

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