Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

IP geolocation: city, region, country and coordinates

ip_geolocate
Read-only

Geolocate an IPv4 or IPv6 address to its city, region, country (code and name), continent and approximate latitude and longitude, with the range the record covers, from DB-IP's City Lite data (CC BY 4.0, monthly; attributed in every answer). An HTTP call without ip answers for the caller's own address. City level at best; private addresses are refused. Use to localise a visitor or caller, or enrich logs; for the network owner use ip_lookup. Example: ip=8.8.8.8. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
ipNoPublic IPv4 or IPv6 address (over HTTP, left out: the caller's own address)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Well beyond the annotations, it discloses pricing ($0.01/call, first 25 free, failed calls free), the data source and license (DB-IP City Lite, CC BY 4.0, monthly, attributed in every answer), an accuracy ceiling ('city level at best'), and that private addresses are refused. It also implicitly explains the non-idempotent hint by noting each call is charged, which is genuinely useful context beyond readOnlyHint/openWorldHint. The only gap is that it does not describe the response shape or how a failed/refused lookup is reported.

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 usage routing, then caveats and cost — a sensible information order with no filler sentences. It is dense to the point of being a run-on, packing license, pricing, and attribution into a single paragraph, but each clause carries information an agent or caller needs.

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 no output schema, the definition covers return fields, accuracy limits, refusal behavior, cost model, and data provenance — enough to call it correctly and interpret results. Nothing material is missing.

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 single 'ip' parameter and its default (caller's own address over HTTP) are already documented in structured data. The description adds only a concrete example (ip=8.8.8.8) and restates the caller-address default, which is marginal value. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

Opens with a specific verb (geolocate) and resource (IPv4/IPv6 address) and enumerates the returned fields: city, region, country code and name, continent, approximate lat/long, and the record's range. It also explicitly differentiates from the sibling ip_lookup ('for the network owner use ip_lookup'), so an agent can select it without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit use cases ('localise a visitor or caller, or enrich logs'), names the alternative tool and the condition that selects it ('for the network owner use ip_lookup'), and states the no-argument behavior for HTTP callers. Nothing about when to reach for this tool is left 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.