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, and the other retrieves the current time in a specific 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 tool names 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 2 tools, the server feels thin for a time-related domain. While the tools cover basic time conversion and current time retrieval, there are likely missing operations such as time calculations, scheduling, or handling date formats, which could limit functionality for agents.
The tool surface is severely incomplete for a time server. It lacks essential operations like adding/subtracting time, parsing dates, formatting times, or handling recurring events. Agents will encounter dead ends when trying to perform common time-related tasks beyond the two provided tools.