Skip to main content
Glama

net_tools_blacklist_check

[$x402 pago por llamada] Consulta si una IPv4 está en la blacklist de Spamhaus ZEN (DNSBL).

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": "net_tools_blacklist_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesDirección IPv4 (IPv6 no soportado).
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It does add genuinely useful behavioral context — that the call is paid per invocation via x402 — which the schema alone only hints at. However, it never says what the response contains (listed/not-listed, return codes, DNSBL reason codes) or whether results can be cached, leaving real gaps for a lookup tool.

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?

A single front-loaded sentence with the payment caveat up front and zero padding. Slightly terse rather than verbose; the bracketed payment tag is the only non-essential element.

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 two-parameter read-style lookup with no annotations and no output schema, an agent still lacks knowledge of what a successful response looks like or what a payment failure returns beyond the schema note. Adequate but not complete.

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%, including the IPv4-only constraint and the x_payment fallback behavior, so the baseline is 3. The description adds nothing about parameter meaning beyond restating the IPv4 input.

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: queries whether an IPv4 is listed in Spamhaus ZEN (DNSBL). An agent can tell this apart from generic siblings like net_tools_dns_lookup or net_tools_email_auth_check because the blacklist source is named. No explicit sibling comparison, so not a 5.

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?

There is no guidance on when to reach for this versus net_tools_email_auth_check or net_tools_dns_lookup, nor any note about prerequisites such as needing a paid header or rate limits. The use case is implied only by the resource name.

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