Alan's Date Time MCP
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_dateA | Get the current date only (e.g. 2025-03-15) |
| get_timeA | Get the current time only (e.g. 14:30:00) |
| get_datetimeB | Get the current date and time (e.g. 2025-03-15 14:30:00) |
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 returns a distinct subset of the current date/time: date only, time only, or both. There is no overlap or ambiguity between them.
All tool names follow the exact same get_<resource> pattern with clear, descriptive nouns. The naming is perfectly uniform and predictable.
Three tools fully cover the trivial domain of fetching date/time information. The count is minimal but complete, with no redundant tools.
The server provides all practical variants (date, time, and combined datetime). There are no obvious missing operations for a date/time utility server.