Skip to main content
Glama

Geoloc

geoloc
Read-onlyIdempotent

"What country is IP [X] in" / "geolocate [IP]" / "RIR country for [resource]", country geolocation of an IP or prefix derived from RIR registration data. NOTE: registration-based geo, not GeoIP, accurate for ownership country but not necessarily the host's physical location. Use for compliance / jurisdiction questions where registry truth matters.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
resourceYesIP or prefix

Output Schema

NameRequiredDescriptionDefault
dataNoCountry geolocation from RIR registration
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "resource": "8.8.8.8"
      +  },
      +  {
      +    "resource": "1.1.1.0/24"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Country geolocation from RIR registration",
      +      "type": "object"
      +    },
      +    "status": {
      +      "description": "API response status",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantive behavior the agent could not otherwise know: results are registration-derived, so ownership country is accurate but physical host location may not be. That caveat is exactly the kind of semantic limitation structured fields cannot express.

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?

The definition leads with the core capability, then the critical caveat, then the intended use case — a sensible ordering. The slash-delimited trigger phrases are dense but serve intent matching; the only minor waste is slight repetition between "derived from RIR registration data" and "registration-based geo".

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 tool with an output schema and full annotations, nothing an agent needs is missing: input types, data provenance, accuracy limits, and the intended decision context are all stated. Return-value details are correctly left to the output schema.

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% for the single required 'resource' field, so the schema already carries the parameter meaning. The description reinforces that prefixes (not just bare IPs) are accepted via the '1.1.1.0/24'-style phrasing and the "IP or prefix" wording, but adds no new format or validation detail. Baseline 3 applies.

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?

The description names a specific resource and output (country geolocation of an IP or prefix) and its data source (RIR registration data). It also front-loads real user phrasings ("What country is IP [X] in", "RIR country for [resource]"), so an agent can match intent 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 Guidelines4/5

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

It gives an explicit when-to-use: compliance / jurisdiction questions where registry truth matters. It also implicitly excludes physical-location use by cautioning that this is not GeoIP. It does not name a sibling alternative for host-location lookups, so the routing guidance stops short of a full 5.

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.