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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| current_timeB | Get the current date and time. |
| relative_timeB | Get the relative time from now. |
| days_in_monthA | Get the number of days in a month. If no date is provided, get the number of days in the current month. |
| get_timestampC | Get the timestamp for the time. |
| convert_timeB | Convert time between timezones. |
| get_week_yearC | Get the week and isoWeek of the year. |
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 6 tools
Most tools have distinct purposes, such as time conversion, current time retrieval, and timestamp generation. However, 'get_week_year' and 'relative_time' could be slightly ambiguous in scope, as both relate to temporal positioning, but their descriptions clarify the differences well.
The tools follow a consistent verb_noun pattern (e.g., convert_time, current_time) with clear, descriptive names. There are minor deviations like 'days_in_month' using plural form, but overall, the naming is highly readable and predictable.
With 6 tools, the server is well-scoped for time-related operations, covering core functionalities like conversion, current time, and date calculations. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset covers basic time operations but has notable gaps, such as missing date arithmetic (e.g., add/subtract days), time formatting, or scheduling tasks. While agents can work around this for simple queries, more complex time manipulations are not supported.