Skip to main content
Glama
World Time MCP Server

World Time MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Tells the current time in cities around the world and converts times between cities. Cities can be qualified with a country or US state, e.g. 'Paris, France' or 'Portland, OR'. IANA time zone names such as 'Asia/Colombo' are also accepted.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_timeA

Get the current local time in a city (or IANA time zone).

Args: city: City name, optionally with a country or US state, e.g. "Colombo", "London, Canada", "Portland, OR", or an IANA zone like "Asia/Tokyo".

compare_timesA

Get the current local time in several cities at once.

Args: cities: City names or IANA zones, e.g. ["Colombo", "London", "New York"].

convert_timeA

Convert a time in one city to the local time in another city.

Args: time: Time in the source city: "14:30", "2:30 PM", or "2026-03-29 14:30" / "2026-03-29 2:30 PM" for a specific date. Time-only values are taken as today in from_city. from_city: City (or IANA zone) the time belongs to. to_city: City (or IANA zone) to convert the time to.

find_citiesA

List cities matching a name, largest first, with their time zones.

Useful when a name is ambiguous (e.g. "Paris" or "Springfield").

Args: query: City name, optionally with a country or US state after a comma. limit: Maximum number of results (1-25).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a reasonably distinct purpose: get_time for one city's current time, convert_time for translating a specific time between cities, compare_times for a multi-city snapshot, and find_cities for resolving ambiguous names. The only mild overlap is get_time vs. compare_times, since the latter is effectively a batch version of the former, but the singular/plural distinction is easy to infer.

Naming Consistency5/5

All four tools follow a consistent verb_noun snake_case pattern: get_time, convert_time, compare_times, find_cities. No mixed conventions or vague verbs.

Tool Count5/5

Four tools is a tight, well-scoped surface for a world-time server, and each one earns its place (lookup, single-city time, conversion, multi-city comparison). Nothing appears redundant or missing from a count perspective.

Completeness4/5

The surface covers the core lifecycle: resolve a city, get current time, convert a time, and compare multiple cities. Minor gaps exist, such as computing elapsed duration or difference between two arbitrary times, but agents can approximate these with convert_time.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues