Skip to main content
Glama

IP Geolocation Payment Quote

ip_geo_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/ip/geo (base $0.004; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?ip=1.1.1.1 (one public IPv4 or IPv6 address). Country code and autonomous system (ASN number and organisation) for one public IPv4 or IPv6 address, from the bundled DB-IP Lite country and ASN databases, updated monthly. Approximate, and never a street address or a person. Do not use it to identify or locate an individual. IP Geolocation by DB-IP, https://db-ip.com, CC BY 4.0. Private or reserved addresses and bad input: not charged. USDC on Base only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ip_geo_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds genuinely new behavioral facts: the exact base price ($0.004), the payment rail (USDC on Base only), the fact it never executes the check or pays, the no-charge cases, and the data provenance/accuracy caveats (DB-IP Lite, updated monthly, approximate). The one ambiguity is that it describes an external HTTP endpoint while annotations set openWorldHint=false — not a contradiction, since the tool itself performs no fetch, but it is a tension an agent must resolve.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense paragraph that mixes capability, pricing, payment protocol, licensing attribution, and a data-quality caveat, with "USDC on Base only" stated twice. The key fact (returns terms, never executes) is front-loaded, but the DB-IP / CC BY 4.0 attribution sits mid-paragraph where it interrupts the operational content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey what comes back; it names the price and currency/network but never describes the response shape (fields, expiry, payment requirement object), leaving an agent to discover it. For a zero-parameter quote tool whose siblings presumably share a response contract, this is workable but incomplete.

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?

With zero input parameters the baseline is 4, but the description introduces an input-shaped token that does not exist in the schema: "GET ?ip=1.1.1.1 (one public IPv4 or IPv6 address)." That is context for a follow-up HTTP call, not a tool argument, yet it reads as a parameter spec, which can mislead an agent into trying to pass an IP. The IPv4/IPv6 requirement is useful, but it belongs to a different call surface.

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

Purpose3/5

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

The first clause is specific: "Returns the payment terms for https://horizonpulse.dev/api/ip/geo ... this tool never runs the check or pays." That distinguishes a quote tool from an execution tool. However, the majority of the description then details the *underlying service's* output (country code, ASN, databases), which can leave an agent unsure whether this tool geolocates or merely prices the call. No sibling is named, even though the catalog is full of parallel *_quote tools that would make the distinction trivial.

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 ("payment terms for ... ip/geo") rather than stated as a when-to-use rule, and no alternative sibling is referenced. The description does supply an explicit when-NOT: "Do not use it to identify or locate an individual," plus an edge case ("Private or reserved addresses and bad input: not charged"). That is real guidance, but it covers only one exclusion, not the selection decision between this and other quote tools.

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.