Skip to main content
Glama

Agent Exchange store

ip_lookup

$0.002 via x402: One IPv4 or IPv6 address in full: announcing ASN and holder, announced prefix, RPKI validity of that announcement, geolocation (country, city, coordinates) from RIPEstat, abuse contact, and the registry block from RDAP (name, country, range, handle). Pay 0.002 USDC through https://store.agentexchange.work/gw/ip/lookup?addr=1.1.1.1 Via the Agent Exchange store gateway; settled by Coinbase.

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": {
      "addr": "<addr>"
    },
    "name": "ip_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrYesIPv4 or IPv6 address
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full disclosure burden. It does surface genuinely useful behavior: the tool is paid ($0.002 via x402/USDC), requires a signed payment payload, and draws from RIPEstat and RDAP. It omits error behavior, rate limits, and what a failed or unpaid call actually returns.

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 intent is front-loaded with the price, but the body is a single dense run-on listing data sources with an embedded payment URL and 'settled by Coinbase' tail. It is functional but the invocation essentials are buried inside the enumeration.

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?

With no output schema and no annotations, the description compensates well by enumerating the return fields (ASN, prefix, RPKI, geo, abuse contact, RDAP block) and explaining the payment flow. For a paid lookup tool this is close to complete, with only failure/pagination behavior 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%, so the schema already documents both addr and x_payment, establishing the baseline of 3. The description restates 'IPv4 or IPv6 address' but adds no format or syntax detail beyond the schema, and says nothing extra about the payment parameter.

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

Purpose4/5

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

The description names a specific resource (one IPv4/IPv6 address) and enumerates exactly what is returned: ASN/holder, prefix, RPKI validity, geolocation, abuse contact, RDAP registry block. This goes well beyond a tautology and is more specific than the sibling name ip_lookup would imply. It only stops short of explicitly distinguishing itself from ip_asn or ip_block.

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

Usage Guidelines2/5

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

It explains the pricing and payment path but gives no when-to-use or when-not-to-use guidance, and never mentions the obvious alternatives ip_asn or ip_block that appear as siblings. The agent cannot tell from the text whether this returns a superset of those tools or a different slice.

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