MCP Simple Timeserver
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_local_timeA | Returns the current local time and timezone information from your local machine. This helps you understand what time it is for the user you're assisting. |
| get_utcA | Returns accurate UTC time from an NTP server. This provides a universal time reference regardless of local timezone. :param server: NTP server address (default: pool.ntp.org) |
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: get_local_time provides local time with timezone information, while get_utc provides universal time from an NTP server. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun naming pattern (get_local_time, get_utc) with the same verb 'get' and clear noun objects. The naming is perfectly uniform and predictable.
With only 2 tools, the server feels somewhat thin for a timeserver domain. While the tools cover basic time retrieval, additional functionality like time conversion, formatting, or scheduling might be expected but is missing.
The server provides core time retrieval functions (local and UTC), but lacks operations for time manipulation, conversion between timezones, or date calculations. These gaps limit the server's utility for more complex time-related tasks.