Skip to main content
Glama

Abuse Contact

abuse_contact
Read-onlyIdempotent

"Abuse contact for IP [X]" / "where to report abuse on [IP / ASN]" / "report spam from [resource]", official abuse-contact email(s) for an IP, prefix, or ASN drawn from RIR records (inetnum / aut-num objects). Use for spam/abuse/DDoS report routing.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "8.8.8.0/24"
    },
    "name": "abuse_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesIP, prefix, or ASN

Output Schema

NameRequiredDescriptionDefault
dataNoAbuse contact email(s) from inetnum/aut-num records
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "resource": "8.8.8.0/24"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Abuse contact email(s) from inetnum/aut-num records",
      +      "type": "object"
      +    },
      +    "status": {
      +      "description": "API response status",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is the provenance and shape of the answer: contacts are drawn from RIR inetnum/aut-num records. It does not say what happens when no abuse contact exists or how multiple emails are returned, though the output schema partly covers the latter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The quoted user phrasings front-load trigger language useful for matching, but the slash-delimited run-on sentence is hard to parse and repeats the resource enumeration that appears again later in the sentence. The core statement (abuse contacts from RIR records) is buried mid-string rather than leading.

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 with an output schema and full annotation coverage, the description supplies what matters: the authoritative data source and the intended use. Only edge-case behavior (no contact on record, multiple contacts) is left unaddressed.

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% and the single parameter already declares "IP, prefix, or ASN", so the description adds little beyond restating that in the prose and the example. Baseline 3 applies since the schema carries the parameter semantics.

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?

The description states a specific resource (official abuse-contact email(s)) and the exact inputs it resolves (IP, prefix, or ASN), plus the authoritative source (RIR inetnum / aut-num objects). That distinguishes it from siblings such as geoloc, network_info, or as_overview, which return different data about the same inputs.

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

Usage Guidelines4/5

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

It gives a clear use case ("Use for spam/abuse/DDoS report routing") and frames the trigger intents ("where to report abuse on [IP / ASN]", "report spam from [resource]"). There is no explicit when-not guidance or named alternative for adjacent questions (e.g. ownership or geolocation lookups), which keeps it below a 5.

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.