Skip to main content
Glama

IP and Host Geolocation

ip_lookup
Read-onlyIdempotent

Resolve an IP address or domain name to its network operator and approximate location: ASN, organization, country, region, city, coordinates, and timezone. Domains are resolved to their first IPv4 address before lookup. Location is IP-level and approximate; it is not the address of the site owner.

Related: dns, whois, ns_reverse.

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

Input Schema

NameRequiredDescriptionDefault
queryYesIP address or domain name. Scheme, port, path, and a leading www. are stripped automatically

Output Schema

NameRequiredDescriptionDefault
dataNoZero or one record
errorNo
totalNo1 when the address is in the database, 0 when it is not
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed2 schema fields changed
    • changedOutput schema / properties / data / items / properties / latitude / description
      Previous value: -"Null when unknown, never 0 (which is a real coordinate)"New value: +"Null when unknown (0 is a real coordinate, so it is not used as a placeholder)"
    • changedOutput schema / properties / data / items / properties / longitude / description
      Previous value: -"Null when unknown, never 0 (which is a real coordinate)"New value: +"Null when unknown (0 is a real coordinate, so it is not used as a placeholder)"
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, idempotent, non-destructive, so the description is not burdened with safety disclosure. It adds real value on top: the pre-lookup resolution of domains to a first IPv4 address, and the interpretive caveat that the location is IP-level and approximate rather than the site owner's address. What is missing is edge-case behavior for private, reserved, or unresolvable addresses.

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?

Three sentences that are front-loaded with the verb and the returned fields, followed by the domain-resolution rule and the accuracy caveat, plus a compact related-tools pointer. No sentence restates the title or the schema, and nothing is padding.

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?

An output schema exists, so return-shape explanation is correctly omitted, and the description covers input coercion, accuracy expectations, and neighboring tools. For a one-parameter read-only lookup this is nearly complete; only failure modes (invalid input, private ranges, no-geo results) are left unstated.

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% with a single required parameter, so the baseline would be 3. The description earns the extra point by explaining what actually happens to a domain input (resolved to its first IPv4 before lookup), which is semantics the schema's stripping note does not cover.

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?

States a precise verb ('Resolve') and resource ('IP address or domain name') and enumerates exactly what comes back: ASN, organization, country, region, city, coordinates, timezone. The closing 'Related: dns, whois, ns_reverse' signals neighboring tools but does not articulate how this one differs from them, so sibling differentiation is gestured at rather than achieved.

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?

The 'Related:' line implies these are adjacent lookups, but there is no explicit when-to-use-this-vs-that statement, no exclusion such as 'use whois for registration data'. The domain-handling note ('Domains are resolved to their first IPv4 address') does clarify an important input case, which lifts it above pure absence of guidance.

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.