time-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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_timeC | Get the current date and time. |
| relative_timeC | 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_timestampD | Get the timestamp for the time. |
| convert_timeC | 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
Each tool has a clearly distinct purpose with no overlap: converting timezones, getting current time, calculating days in a month, generating timestamps, determining week/year, and computing relative time. The descriptions are specific enough to prevent confusion between tools.
Most tools follow a consistent verb_noun pattern (e.g., convert_time, get_timestamp), but 'current_time' and 'relative_time' deviate slightly by using adjectives instead of verbs. The naming is still readable and predictable overall.
With 6 tools, the server is well-scoped for time-related operations. Each tool serves a unique and useful function, avoiding bloat while covering common time manipulation needs effectively.
The toolset covers core time operations like conversion, current time, and relative calculations, but lacks explicit CRUD for time data (e.g., scheduling or event management). Minor gaps exist, but agents can work around them for most time-related tasks.