IPGeolocation MCP Server

Timezone Lookup

get_timezone

Read-only

Read-only timezone lookup via GET /v3/timezone. Works on free and paid plans. Cost: 1 credit. This endpoint provides current local time and metadata for one place, IP, airport, UN/LOCODE, or IANA timezone; convert_timezone provides…

Instructions

Returns { time_zone } plus selector context such as location, airport, city, or ip. time_zone includes the zone name, current time, UTC offsets, date/time variants, abbreviations, and DST status/transition fields when available.

Selector priority is tz, lat/long, location, ip, iata_code, icao_code, then lo_code. lat and long must be provided together. lang only changes location fields; non-English lang is paid-only and returns 401 on free plans.

Input Schema

Name	Required	Description
`ip`	No	IPv4 or IPv6 address to get timezone for.
`tz`	No	IANA timezone name (e.g. America/New_York, Europe/London). Highest priority if multiple params provided.
`lat`	No	Latitude coordinate. Must be used together with long.
`lang`	No	Response language for location fields in IP-based lookups (en, de, ru, ja, fr, cn, es, cs, it, ko, fa, pt, ar). Paid plans only. Free plan returns 401 for non-English language values.
`long`	No	Longitude coordinate. Must be used together with lat.
`lo_code`	No	5-character UN/LOCODE (e.g. DEBER, USNYC).
`location`	No	City or address string (e.g. London, UK).
`iata_code`	No	3-letter IATA airport code (e.g. JFK, LHR). Returns airport details in the response.
`icao_code`	No	4-letter ICAO airport code (e.g. KJFK, EGLL). Returns airport details in the response.

Output Schema

Name	Required	Description
`data`	No	Present on success: API result after field selection, redaction, and transport limits.
`page`	No
`error`	No	Present on failure, with isError: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.3Oct 28, 2026

removedOutput schema / properties / data / additionalProperties / anyOf

Removed value: -[
-  {
-    "type": "null"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "object"
-  }
-]

addedOutput schema / properties / data / additionalProperties / type

Added value: +[
+  "null",
+  "boolean",
+  "number",
+  "string",
+  "array",
+  "object"
+]

Addedv2.0.1Oct 13, 2026
Removedv2.0.0Jul 25, 2026
First observedv1.0.10Mar 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint, yet the description adds cost (1 credit), plan gating with the specific 401 failure mode, selector priority ordering when multiple params are supplied, and the lat/long pairing constraint. That is substantive behavior beyond structured fields.

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-loaded with purpose and sibling disambiguation, and the priority/constraint sentences earn their space. The paragraph detailing time_zone sub-fields is partially redundant given an output schema exists, which costs a point on tightness.

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 9-parameter, all-optional selector tool, the description covers plan gating, cost, precedence, pairing constraints, and the shape of the union return. Nothing an agent needs in order to pick a selector and call correctly is missing.

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 baseline is 3, but the description adds the precedence chain (tz, lat/long, location, ip, iata_code, icao_code, lo_code) and clarifies that lang only affects location fields rather than the whole response. These are semantics the schema does not state in one place.

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?

States a specific verb and resource ('Read-only timezone lookup via GET /v3/timezone') and enumerates the accepted inputs (place, IP, airport, UN/LOCODE, IANA timezone). It explicitly separates itself from the nearest sibling: 'convert_timezone provides source-to-destination conversion.'

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 operating context: works on free and paid plans, costs 1 credit, and lang is paid-only (401 on free). It names convert_timezone as the alternative for conversion, but does not address how this differs from the sibling lookup_ip, which plausibly also yields timezone data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server