Date-Time 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_datetimeA | Returns the current date and time in ISO 8601 format |
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. The tool's purpose is clear and distinct.
The single tool name 'get_current_datetime' follows a clear verb_noun pattern, is descriptive, and uses consistent snake_case. There are no other names to conflict with.
A single tool is on the low end of the spectrum. While it covers a basic need, a date-time server might reasonably include more tools (e.g., timezone conversion, formatting), so the count feels slightly thin.
The server only provides the current date/time, but a typical date-time utility would also handle conversions, formatting, or timezone lookups. This leaves significant gaps for common use cases.