Time MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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.
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 retrieves the current time in a specified timezone. There is no overlap or ambiguity in their functions, 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 and get_current_time), using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions.
With only two tools, the server feels thin for a time-related domain. While the tools cover basic operations, there are likely gaps such as scheduling, time arithmetic, or handling date formats that could enhance functionality. A count of 2 is borderline too few for a comprehensive time server.
The tool surface is significantly incomplete for a time server domain. It lacks essential operations like date manipulation, time arithmetic, scheduling, or handling recurring events. Agents may struggle with common time-related tasks beyond simple conversions and current time retrieval.