datetime-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The custom port to use when TRANSPORT is set to 'http'. Defaults to 3000. | |
| TRANSPORT | No | The transport mode for the server (e.g., 'http'). Defaults to stdio if not specified. |
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 |
|---|---|
| get_current_datetimeA | 获取当前日期和时间，支持自定义格式化。 该工具返回当前的日期时间，可以指定返回的格式。如果不指定格式，默认返回 "yyyy-MM-dd" 格式。 支持的格式占位符:
使用示例:
注意事项:
|
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_current_datetime' has a clear, distinct purpose that cannot be mistaken for any other functionality.
The naming is trivially consistent as there is only one tool. The tool name 'get_current_datetime' follows a clear verb_noun pattern (get + current_datetime), which would be appropriate if more tools were added.
A single tool is too few for a server named 'datetime-mcp-server', which suggests a broader scope for date and time operations. While the tool is functional, the server lacks operations like date parsing, timezone conversion, or date arithmetic, making it feel incomplete and under-scoped.
The server is severely incomplete for a datetime domain. It only provides current datetime retrieval with formatting, missing essential operations such as date manipulation, comparison, parsing from strings, or handling different timezones. This creates significant gaps that would limit agent capabilities in datetime-related tasks.