Time MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| local-timezone | No | IANA timezone name to override the automatically detected system timezone (e.g., 'America/New_York', 'Europe/London'). |
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_timeB | 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 retrieves the current time in a specified timezone. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent verb_noun pattern (convert_time, get_current_time) with clear, descriptive names. The naming style is uniform and predictable across the set.
With only two tools, the server feels thin for a time-related domain. While the tools cover basic operations, the scope is limited, and additional functionalities like scheduling, time calculations, or date manipulations might be expected but are missing.
The tool set is severely incomplete for a time server. It lacks essential operations such as date parsing, time arithmetic, scheduling, or recurring event handling, which are common in time-related applications. This will likely cause agent failures when more complex time tasks are required.