DateTime 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_timeB | Get the current date and time in various formats |
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 and distinct purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The naming follows a clear verb_noun pattern.
A single tool for a DateTime server feels thin and under-scoped. While it covers the basic function of getting the current time, it lacks other common date/time operations like parsing, formatting, or calculations, making the server incomplete for typical use cases.
The server is severely incomplete for a DateTime domain. It only provides current time retrieval, missing essential operations such as date parsing, timezone conversions, date arithmetic, or formatting options beyond 'various formats', which limits its utility.