Skip to main content
Glama

apex-dev

Ip geolocate

ip_geolocate
Read-onlyIdempotent

IP geolocation and ASN lookup for any public IPv4, IPv6, or hostname (country, region, city, lat/lon, timezone, ISP, org, ASN). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
ipYesPublic IPv4/IPv6 address or hostname (e.g. 1.1.1.1).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds the details annotations cannot: a metered cost of $0.001 per call, accepted x402 payment rails (USDC on Arc/Base/Solana, XNT on X1), and the mandatory two-call payment handshake. It does not mention failure modes or rate limits.

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?

Front-loads what the tool returns, then the cost and payment protocol in two tight sentences with no filler. The parenthetical field list is long but earns its place by standing in for a missing output schema.

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?

No output schema exists, so enumerating the response fields is necessary and done. With annotations covering safety and the schema covering inputs, the remaining need is the payment protocol, which is explained. Minor gaps are what happens on an unpaid second call or an invalid address.

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 coverage is 100%, so both parameters are already documented and a 3 would be the floor. The description adds real meaning beyond the schema by explaining that `payment` is intentionally omitted on the first call and supplied on the second, which the schema's one-line description does not convey.

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?

Names a specific verb+resource ('IP geolocation and ASN lookup') and enumerates the returned fields (country, region, city, lat/lon, timezone, ISP, org, ASN), which makes the scope concrete. It never contrasts with the nearest siblings such as whois_lookup or dns_records, so an agent must infer the boundary itself.

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?

Gives clear operational guidance for the unusual part of this tool: call once without `payment` to obtain terms, then call again with `payment`. That is exactly the when/how context an agent needs. It stops short of stating when-not to use it or when a sibling like whois_lookup is preferable.

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