Time MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
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_timeB | Get the current date and time |
| get_time_infoC | Get detailed time information including timezone, day of week, etc. |
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 overlapping purposes: both retrieve time-related information, with 'get_current_time' focusing on basic date/time and 'get_time_info' adding details like timezone and day of week. This creates ambiguity as an agent might struggle to choose between them for general time queries, since their boundaries are unclear and they could be confused for similar tasks.
The tool names follow a consistent verb_noun pattern with 'get_' prefix and snake_case formatting throughout. Both tools start with 'get_' followed by descriptive nouns ('current_time', 'time_info'), making the naming predictable and readable without any deviations or mixed conventions.
With only 2 tools, the server feels too thin for a time-related domain, as it lacks basic operations like time conversion, timezone handling, or scheduling functions. This minimal set limits functionality and suggests an incomplete scope, making it borderline inadequate for typical time management tasks.
The tool surface is significantly incomplete for a time server domain. It only provides retrieval functions without essential operations such as time conversion between zones, date arithmetic, scheduling, or alarm setting. These gaps will likely cause agent failures when trying to perform common time-related workflows beyond simple queries.