Skip to main content
Glama

IP-DB IP Reputation

Check IP reputation

check_ip
Read-onlyIdempotent

Reputation of one IP address from IP-DB: 0-100 abuse confidence score and label, network type (residential, datacenter/hosting, vpn, tor), the threat-intelligence blocklists and DNSBLs that list it, community abuse reports, country, ASN and owner, the network's abuse contact, and a fraud-screening recommendation (allow, review, challenge, block).

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_ip"
  }
}

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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety and idempotence are covered structurally. The description adds real value by enumerating what comes back – the 0-100 abuse confidence score, network type, blocklist and DNSBL hits, community reports, ASN, abuse contact and the allow/review/challenge/block recommendation – which matters because there is no output schema. It says nothing about authentication, rate limits or pagination.

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?

One sentence, front-loaded with the score and label before the long field enumeration. The list is dense but each item is a distinct return value that the absent output schema cannot supply, so it earns its space.

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?

For a single-parameter read-only lookup, the definition covers the input (via schema) and the return surface (via description) adequately. The one real omission is guidance against the check_blacklists sibling, which is the only thing an agent could get wrong here.

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 the single parameter is fully documented, including that IPv4, IPv6 or a hostname to resolve are accepted. The description adds no meaning beyond that, which is the expected baseline when the schema already does the work.

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 names a specific resource and scope – 'Reputation of one IP address from IP-DB' – so an agent knows this is a single-address reputation lookup. It never states a verb ('check', 'look up') and never mentions the sibling check_blacklists, so it doesn't differentiate itself from alternatives, but the core purpose is unmistakable.

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 when-to-use guidance at all. With check_blacklists as a sibling, the description should say when to use this broad reputation lookup versus the narrower blocklist check, and it does not. The agent must infer the choice from the tool names alone.

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