mcp-datetime
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_datetimeA | Get 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 confusion or overlap between tools. The single tool 'get_datetime' has a clear and distinct purpose that cannot be mistaken for any other tool in this set.
The naming pattern is trivially consistent as there is only one tool. The tool name 'get_datetime' follows a clear verb_noun convention, and with no other tools to compare against, it maintains perfect consistency within the set.
A single tool for a datetime server is too minimal for the apparent scope. While 'get_datetime' provides current date and time, a datetime domain typically includes operations like formatting, parsing, timezone conversion, or date arithmetic, making this set feel incomplete and underpowered.
The tool surface is severely incomplete for a datetime server. It only offers getting the current datetime in various formats, lacking essential operations such as parsing strings to dates, converting timezones, calculating date differences, or manipulating dates (e.g., adding days). This will cause significant agent failures in datetime-related tasks.