Ripe Stat

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`resource`	Yes	IP, prefix, or ASN

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Abuse contact email(s) from inetnum/aut-num records
`status`	No	API response status

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

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

First observedMay 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by specifying the data source (RIR records) and output type (official abuse-contact email(s)). No contradictions.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the primary purpose and includes multiple clarifying phrasings. Every part serves a purpose with zero waste.

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?

Given the low complexity (one required parameter, simple lookup), the description sufficiently explains what the tool does and returns. The presence of an output schema further reduces the need to describe return values.

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

Parameters4/5

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

Schema description coverage is 100% for the single parameter 'resource' (described as 'IP, prefix, or ASN'). The description adds an example ('8.8.8.0/24') and clarifies the acceptable formats, adding meaning beyond the schema.

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 clearly states the tool's purpose with specific verbs ('contact', 'report') and resources ('IP, prefix, ASN'). It includes alternative phrasings and distinguishes from sibling tools by focusing on abuse contact lookup from RIR records.

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?

The description explicitly states 'Use for spam/abuse/DDoS report routing', providing clear context. However, it does not mention when not to use the tool or list alternative tools for similar queries.

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

All Ripe Stat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.