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_datetimeB | Get the current date and time |
| get_current_dateA | Get only the current date |
| get_current_timeB | Get only the current 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 3 tools
Each tool has a clearly distinct purpose: get_current_date returns only the date, get_current_datetime returns both date and time, and get_current_time returns only the time. There is no overlap or ambiguity between these three operations.
All tool names follow a consistent verb_noun pattern with 'get_current_' prefix, using snake_case uniformly. This makes the naming predictable and easy to understand.
With only 3 tools, the server feels somewhat thin for a datetime domain, as it lacks operations like date/time parsing, formatting, arithmetic, or timezone handling. However, the tools cover basic current datetime retrieval adequately.
The toolset is severely incomplete for a datetime server, missing essential operations such as date/time manipulation, conversion between formats or timezones, parsing strings, or calculating differences. This will limit agents to only retrieving current values without any processing capabilities.