Skip to main content
Glama

dnsbl_check

Check an IP or domain against major DNS blocklists by querying authoritative nameservers, bypassing open-resolver blocks to reveal spam and threat listings.

Instructions

Check an IP (or domain) against major DNS blocklists via direct DNS queries.

Queries Spamhaus ZEN, Barracuda, SpamCop, SORBS, PSBL and UCEPROTECT, bypassing open-resolver blocks by talking to each zone's authoritative nameservers. Domains are checked against Spamhaus DBL. Some zones may be unreachable.

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": {
      "target": "<target>"
    },
    "name": "dnsbl_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
include_errorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose method (direct authoritative queries, bypassing open-resolver blocks) and a failure mode (some zones may be unreachable). It says nothing about rate limits, expected latency, or what a result looks like, and there is no output schema to fill that 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?

Short and front-loaded, leading with the action and following with the zones and method. The list of blocklists is verbose but earns its place by setting expectations about coverage.

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

Completeness3/5

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

For a reputation-check tool with no annotations and no output schema, key information is absent: the shape of the response (per-zone verdicts, aggregate score, text vs structured) and what 'target' formats are accepted beyond IP-or-domain. The method and partial-failure caveat are helpful but not sufficient.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate and largely does not. It clarifies that 'target' accepts an IP or a domain, but never explains 'include_errors', which is the more ambiguous parameter given the note about unreachable zones.

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 an IP or domain against DNS blocklists, naming the exact zones queried. It does not explicitly distinguish itself from siblings such as tor_exit_check, but the subject matter is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to reach for this tool versus related reputation checks, nor any prerequisites or exclusions. The usage is only inferable from the purpose sentence.

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