time-mcp-local
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_TIMEZONE | No | Override system timezone (e.g., 'America/New_York') | system timezone |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
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 serve clearly distinct purposes: one returns the current time in a given timezone, while the other converts a specific time between timezones. There is no overlap in functionality.
Both tool names follow a consistent verb_noun pattern: 'convert_time' and 'get_current_time'. The naming is predictable and easy to understand.
With only two tools, the surface is quite thin. While it covers basic time operations, a more complete set might include listing timezones or calculating time differences. The count feels borderline for a general-purpose time utility.
The core workflows of getting the current time and converting between timezones are covered. However, missing utilities like listing available timezones or formatting time outputs are minor gaps that agents can typically work around.