Skip to main content
Glama
IPGeolocation MCP Server

IPGeolocation MCP Server

Abuse Contact Lookup

get_abuse_contact
Read-only

Look up abuse contact details for an IPv4 or IPv6 address, including emails, phone numbers, and organization, to report abuse or security incidents.

Instructions

Read-only abuse contact lookup via GET /v3/abuse. Paid only. Cost: 1 credit. This endpoint is dedicated to abuse contact data; lookup_ip with include=abuse provides abuse data together with location, security, company, ASN, timezone, network, or currency.

Returns { ip, abuse } with route, country, name, organization, kind, address, emails, and phone_numbers for reporting abuse.

fields/excludes accept comma-separated abuse.* paths such as abuse.emails; ip is always returned. force_refresh bypasses cached data, makes a new upstream request, and can consume credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_abuse_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoIPv4 or IPv6 address to get abuse contact for. Omit to use the server's public egress IP.
fieldsNoComma-separated abuse fields to return (e.g. abuse.emails,abuse.organization). Reduces response size.
excludesNoComma-separated abuse fields to exclude from response (e.g. abuse.phone_numbers,abuse.address).
force_refreshNoDefault false. When true, bypasses cached abuse contact data; a successful refresh makes a new upstream request and can consume credits.

Output Schema

NameRequiredDescriptionDefault
dataNoPresent on success: API result after field selection, redaction, and transport limits.
pageNo
errorNoPresent on failure, with isError: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.3
    • removedOutput schema / properties / data / additionalProperties / anyOf
      Removed value: -[
      -  {
      -    "type": "null"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "array"
      -  },
      -  {
      -    "type": "object"
      -  }
      -]
    • addedOutput schema / properties / data / additionalProperties / type
      Added value: +[
      +  "null",
      +  "boolean",
      +  "number",
      +  "string",
      +  "array",
      +  "object"
      +]
  2. Addedv2.0.1
  3. Removedv2.0.0
  4. Changed3 schema fields changedv1.0.15
    • changedInput schema / properties / excludes / description
      Previous value: -"Comma-separated fields to exclude from response (e.g. phone_numbers,address)."New value: +"Comma-separated abuse fields to exclude from response (e.g. abuse.phone_numbers,abuse.address)."
    • changedInput schema / properties / fields / description
      Previous value: -"Comma-separated fields to return (e.g. emails,organization). Reduces response size. Works on all plans."New value: +"Comma-separated abuse fields to return (e.g. abuse.emails,abuse.organization). Reduces response size."
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Default false. Leave unset unless the user asks to refresh or rerun."New value: +"Default false. Set true only when the user asks to refresh cached abuse contact data; a successful refresh makes a new upstream request and can consume credits."
  5. First observedv1.0.10

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only carry readOnlyHint and openWorldHint, so the description adds meaningful context: credit cost, that this is a dedicated endpoint, the returned shape, and that force_refresh bypasses the cache and makes a new upstream request that can consume credits. No contradiction with readOnlyHint, since nothing is modified server-side. The caching/refresh disclosure partially duplicates the schema text, keeping it short of a 5.

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 with purpose and cost, then the sibling distinction, then return shape, then parameters — a sensible ordering with no filler. Minor redundancy: the force_refresh explanation restates the schema description almost verbatim.

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?

For a read-only, zero-required-parameter lookup with an output schema and full parameter coverage, nothing an agent needs is missing: cost, alternative route, response shape, and cache/refresh semantics are all present. The return-value detail is a bonus beyond what the output schema alone would require.

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%, so all four parameters are already documented in the schema. The description reinforces the abuse.* path convention for fields/excludes and states ip is always returned, but adds no field names, defaults, or syntax beyond what the schema provides — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (read-only abuse contact lookup via GET /v3/abuse) and immediately distinguishes it from the closest sibling: lookup_ip with include=abuse returns abuse data bundled with location, security, company, ASN, timezone, network, or currency. An agent can pick between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing guidance to the alternative (lookup_ip with include=abuse) and the condition that selects it (you want abuse data combined with other data sets). It also surfaces the commercial constraint — paid only, 1 credit — which is a real decision factor before calling.

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