Skip to main content
Glama

SouthPow crypto & market data

buy_ip_lookup

Paid. IP address lookup: network owner, organisation, country, address range, reverse DNS (RDAP). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/ip/lookup.

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

Input Schema

NameRequiredDescriptionDefault
ipYesPublic IPv4 or IPv6

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses cost ($0.01 USDC on Base or Solana), payment rails, that no account or API key is required, and that failed calls are not charged. It stops short of describing response format, rate limits, or latency, which keeps it from a 5.

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?

Front-loads the billing signal, then the resource and result fields, then price/auth/refund terms and endpoint. Telegraphic fragments but every clause carries operational information an agent needs before spending money.

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 one-parameter paid lookup with no output schema, the description covers cost, payment method, auth requirements, billing on failure, and the fields returned. Only error behavior and output shape specifics are absent, which is a minor gap.

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 coverage is 100% and there is a single required parameter already described as 'Public IPv4 or IPv6', so the schema does the work; the description adds no format examples or constraints beyond what is structured.

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?

Names a specific verb+resource ('IP address lookup') and enumerates the returned fields (network owner, organisation, country, address range, reverse DNS via RDAP), which lets an agent distinguish it from siblings like buy_domain_whois or buy_domain_dns without opening the schema.

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 by the resource name (an IP lookup) and the 'Paid' marker plus price tells the agent this is a billable call, but there is no explicit statement of when to prefer it or which sibling to use instead (e.g. DNS vs WHOIS vs IP lookup), leaving routing to inference.

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