Skip to main content
Glama

Timezone Converter

timezone_convert
Read-onlyIdempotent

Convert a datetime between timezones using timezone names, coordinates, city addresses, IATA/ICAO codes, or UN/LOCODEs. Specify source and destination with any supported identifier.

Instructions

Convert a date/time from one timezone to another. Specify the source and destination timezone each using ONE of: timezone name (tz_from/tz_to), coordinates (lat/long_from + lat/long_to), city address (location_from/location_to), IATA code (iata_from/iata_to), ICAO code (icao_from/icao_to), or UN/LOCODE (locode_from/locode_to).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeYesDatetime to convert. Formats: 'yyyy-MM-dd HH:mm' or 'yyyy-MM-dd HH:mm:ss'.
tz_fromNoSource timezone name (e.g. 'America/New_York'). Use ONE source type only.
tz_toNoDestination timezone name (e.g. 'Asia/Tokyo'). Use ONE destination type only.
lat_fromNoSource latitude. Must be paired with 'long_from'.
long_fromNoSource longitude. Must be paired with 'lat_from'.
lat_toNoDestination latitude. Must be paired with 'long_to'.
long_toNoDestination longitude. Must be paired with 'lat_to'.
location_fromNoSource city/address (e.g. 'London, UK').
location_toNoDestination city/address (e.g. 'New York, US').
iata_fromNoSource 3-letter IATA airport code (e.g. 'LHR').
iata_toNoDestination 3-letter IATA airport code (e.g. 'JFK').
icao_fromNoSource 4-letter ICAO airport code (e.g. 'EGLL').
icao_toNoDestination 4-letter ICAO airport code (e.g. 'KJFK').
locode_fromNoSource UN/LOCODE (e.g. 'GBLON').
locode_toNoDestination UN/LOCODE (e.g. 'USNYC').
Behavior4/5

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

Annotations provide read-only, idempotent hints. Description adds constraints on parameter grouping (use one type per source/destination) and provides examples, adding value beyond annotations.

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?

Description is two concise sentences, front-loaded with the main action, and no superfluous text.

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?

With 15 parameters and no output schema, the description covers key behavioral rules. Could mention output format, but adequate for most use cases.

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%, but description adds meaning by explaining the grouping logic and providing examples, making parameter usage clearer than schema alone.

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?

Description clearly states 'Convert a date/time from one timezone to another' and lists the multiple ways to specify timezones, distinguishing it from sibling tools like timezone_lookup.

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?

Description specifies that each timezone must be specified using ONE of the listed methods, with clear examples. Doesn't explicitly state when not to use, but the context is clear given sibling tools are different.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/api-freaks/apifreaks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server