Chronos Protocol
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 |
|---|---|
| get_current_timeB | Get current time (defaults to system time, supports any timezone) |
| convert_timeB | Convert time between timezones (defaults to system time for source/target) |
| start_activity_logC | Start a new activity log with system timestamp and unique Time ID |
| end_activity_logC | End an activity log with system timestamp and calculate duration |
| get_elapsed_timeC | Get the elapsed time for an ongoing or completed activity |
| get_activity_logsC | Retrieve activity logs with optional filtering |
| update_activity_logC | Update an existing activity log |
| create_time_reminderC | Create a time-based reminder using system time for scheduling |
| check_time_remindersC | Check for due or upcoming time reminders |
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 9 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools like 'check_time_reminders', 'create_time_reminder', 'get_current_time', and 'convert_time' each handle specific time-related tasks, while 'start_activity_log', 'end_activity_log', 'get_activity_logs', 'update_activity_log', and 'get_elapsed_time' form a complete activity logging lifecycle. There is no overlap in functionality that could cause misselection.
All tool names follow a consistent verb_noun pattern with snake_case throughout. Examples include 'check_time_reminders', 'convert_time', 'create_time_reminder', 'start_activity_log', and 'update_activity_log'. This predictability makes it easy for agents to understand and use the tools without confusion from mixed conventions.
With 9 tools, the count is well-scoped for the server's purpose of time management and activity logging. Each tool earns its place by covering distinct aspects such as time retrieval, conversion, reminders, and activity tracking. This number is neither too thin nor too heavy, fitting typical expectations for a focused domain.
The tool set provides complete CRUD/lifecycle coverage for both time management and activity logging domains. For time, it includes creation, checking, conversion, and retrieval. For activities, it supports starting, ending, updating, retrieving, and calculating elapsed time. There are no obvious gaps or dead ends that would cause agent failures.