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., 'Asia/Shanghai', 'America/New_York'). |
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 current time in a specific 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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose that cannot be confused with any other tool in the set.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'get_current_time' follows a clear verb_noun pattern, but consistency cannot be assessed across a set of one.
A single tool for a time server is too few for the apparent scope, as time-related operations typically include more functionality (e.g., time conversion, scheduling, or date calculations). This minimal set feels thin and underdeveloped for the domain.
The tool set is severely incomplete for a time server, covering only current time retrieval in specific timezones. Obvious gaps include time conversion between zones, date arithmetic, scheduling, or historical time data, which agents would need for common time-related tasks.