datetime-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TZ | No | Default IANA timezone | Australia/Perth |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| datetime.nowD | – |
| datetime.healthD | – |
| datetime.parseD | – |
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
The three tools have clearly distinct purposes: health likely checks server status, now retrieves the current datetime, and parse converts datetime strings. There is no overlap or ambiguity between these functions.
All tool names follow a consistent pattern with a common prefix 'datetime.' and clear, concise suffixes (health, now, parse). This uniformity makes the set predictable and easy to understand.
Three tools is a borderline count for a datetime server; it covers basic operations but feels thin, potentially lacking advanced features like formatting, timezone handling, or date arithmetic that might be expected in this domain.
The tool set is significantly incomplete for datetime operations; it includes core functions (now, parse) but lacks essential tools for formatting, timezone conversion, date arithmetic, or validation, which are common in datetime libraries and could cause agent failures.