Skip to main content
Glama
duksh

PeerGlass

by duksh

rir_get_abuse_contact

Read-onlyIdempotent

Find abuse contacts for IP addresses by querying Regional Internet Registries. Use to report network abuse like spam or DDoS attacks.

Instructions

Find the abuse contact for any IP address globally using IANA bootstrap routing.

Uses IANA RDAP Bootstrap to identify the authoritative RIR first (efficient), then queries only that RIR. Falls back to querying all 5 if bootstrap fails. Extracts abuse contacts from entity roles: 'abuse', 'technical', 'noc'.

Use this tool as the first step in any network abuse reporting workflow: spam, DDoS attacks, port scanning, credential stuffing, etc.

Results are cached for 1 hour.

Args: params (AbuseContactInput): - ip_address (str): IPv4 or IPv6 address (e.g. '185.220.101.1')

Returns: str: Markdown report with abuse email(s), phone(s), network name, organization, country, and authoritative RIR. JSON schema: { "ip_address": str, "authoritative_rir": str, "abuse_email": [str], "abuse_phone": [str], "network_name": str, "org_name": str, "country": str }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (readOnly/idempotent), description details algorithm ('IANA RDAP Bootstrap... Falls back to querying all 5'), data extraction logic ('entity roles: abuse, technical, noc'), and caching behavior ('cached for 1 hour'). No contradictions with annotations.

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?

Well-structured docstring format with Purpose → Mechanism → Usage → Caching → Args → Returns. Every sentence earns its place; technical details (bootstrap logic, fallback, caching) are essential for an external-query tool. No fluff.

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 complex external dependencies (5 RIRs, bootstrap protocol) and rich output, description provides complete picture: input spec, detailed JSON output schema, error-handling strategy (fallback), and caching policy. Fully sufficient for invocation.

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?

With claimed 0% schema coverage, the Args section compensates by documenting the single parameter with type (str) and format example ('185.220.101.1'). Would benefit from mentioning IPv6 format specifics, but adequately covers the input 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?

Description opens with specific verb 'Find' and resource 'abuse contact for any IP address', plus distinguishes method 'using IANA bootstrap routing'. Explicitly differentiates from sibling RIR tools by focusing specifically on abuse contact extraction.

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?

Explicitly states 'Use this tool as the first step in any network abuse reporting workflow' followed by concrete scenarios (spam, DDoS, port scanning). Clear value proposition for when to select this over other network tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/duksh/peerglass'

If you have feedback or need assistance with the MCP directory API, please join our Discord server