Time MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP listen address (HTTP mode) | 0.0.0.0 |
| PORT | No | HTTP port (HTTP mode) | 3000 |
| API_PATH | No | HTTP API path (HTTP mode) | /mcp |
| MCP_PATH | No | HTTP API path (HTTP mode) | /mcp |
| LOG_LEVEL | No | Log level (DEBUG | INFO | WARN | ERROR) | INFO |
| TRANSPORT | No | Transport type (stdio | http) | stdio |
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 |
|---|---|
| getCurrentTimeA | Get the current UTC time in ISO 8601 format along with Unix timestamp |
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 tool's purpose is singular and clearly defined.
A single tool inherently has perfect naming consistency. The name 'getCurrentTime' follows a clear verb_noun pattern and is descriptive.
One tool is too few for most server purposes, as it limits functionality and may not cover the domain adequately. For a time-related server, additional tools like time conversion, timezone handling, or scheduling might be expected.
The server is severely incomplete for a time-related domain. It only provides current time retrieval, lacking essential operations such as timezone conversions, date calculations, or formatting options, which are common in time utilities.