Time-Zone
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 |
|---|---|
| get_current_timeC | 获取指定时区的当前时间 |
| convert_timeC | 在不同时区之间转换时间 |
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 2 tools
The two tools have clearly distinct purposes: convert_time handles time conversion between time zones, while get_current_time retrieves the current time in a specified time zone. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun naming pattern (convert_time and get_current_time), using snake_case throughout. The naming is predictable and readable without any deviations.
With only 2 tools, the server feels thin for a time zone domain, as it lacks operations like listing available time zones, handling daylight saving time, or providing time zone information. The count is too low for comprehensive coverage.
The tool surface is significantly incomplete for time zone management. It lacks basic operations such as listing time zones, getting time zone details, or handling date-time formatting, which are essential for typical time-related workflows and will likely cause agent failures.