Time-MCP
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_timeA | Get the current date and time |
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 'get_time' has a clear and distinct purpose.
The tool name 'get_time' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations.
A single tool is too few for most practical server purposes, making the set feel thin and limited. While it might suffice for a trivial time-checking function, it lacks depth for broader time-related operations.
The server's domain appears to be time-related, but with only a 'get_time' tool, there are significant gaps. Missing operations like time conversion, scheduling, or timezone handling make the surface severely incomplete for typical time management tasks.