Skip to main content
Glama

Who owns an IP address: network name, CIDR, owner, abuse

ip
Read-only

Who owns an IP address: network name, CIDR, owner, abuse contact (RDAP), ASN and holder (RIPEstat), and reverse DNS. Private, reserved and documentation addresses are refused with 400. Public registry data only. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 or IPv6 address

Output Schema

NameRequiredDescriptionDefault
ipNo
asnNo
ownerNo
sourceNo
networkNo
versionNo
checkedAtNo
reverseDnsNo
abuseContactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses failure behavior (private, reserved and documentation addresses rejected with 400), the data provenance constraint (public registry data only), and the full payment model including the exact price, the x402/USDC mechanism, supported chains, and the fact that failed calls are not charged. That is unusually rich disclosure of cost and error semantics that annotations cannot express.

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?

Three tight sentences, front-loaded with the payload the caller gets, followed by the refusal rule and the pricing. Every sentence carries information, though the pricing sentence is long and could be trimmed slightly without loss.

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 one-parameter read-only lookup with an output schema, the description covers everything an agent needs before calling: what data is returned, which inputs will be rejected, that only public registry data is used, and that the call costs money. Return-value formatting is correctly left to the output schema.

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?

There is a single required parameter with 100% schema description coverage, so the schema already states 'IPv4 or IPv6 address' and sets the baseline. The description adds no syntax, normalization, or CIDR/range handling detail beyond what the schema provides.

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 title and first sentence state a specific lookup: ownership data for an IP address, enumerating exactly what comes back (network name, CIDR, owner, abuse contact via RDAP, ASN/holder via RIPEstat, reverse DNS). The name 'ip' alone is ambiguous, but the description resolves it into an unambiguous resource+verb, and the enumerated data sources distinguish it from siblings like dns or address_parse.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool only works for public addresses, and private/reserved/documentation ranges are refused with 400, which tells the agent when the call will fail. However, there is no explicit routing guidance against the obvious alternatives (dns, address_parse), which an agent must infer from the sibling 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