Time MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_TIMEZONE | No | Override the system timezone detection with a specific IANA timezone name (e.g., 'America/New_York') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_timeC | Get current time in a specific timezones |
| convert_timeC | Convert time between timezones |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one converts time between timezones, while the other gets the current time in a specific timezone. There is no overlap or ambiguity in functionality.
Both tools follow a consistent verb_noun pattern (convert_time, get_current_time) with clear, descriptive names that align well with their functions.
With only 2 tools, the server feels thin for a time-related domain. It lacks basic operations like formatting time, calculating time differences, or handling date ranges, which are common in time utilities.
The tool surface is severely incomplete for a time server. It misses essential functions such as parsing dates, adding/subtracting time intervals, comparing times, or supporting common date formats, limiting agent capabilities.