chron
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP mode | 3001 |
| CHRON_API_KEY | No | Bearer token for HTTP mode | |
| CHRON_DB_PATH | No | Path to SQLite database file | ~/.chron/chron.db |
| CHRON_TRANSPORT | No | Set to 'http' to enable HTTP+SSE mode | stdio |
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 |
|---|---|
| start_sessionA | Create a new audit session or resume an existing one by title. Call this at the start of every conversation. |
| log_messageA | Record a single message (user or assistant) with the current local datetime and timezone offset. Call before responding for user messages, and before sending for assistant messages. |
| log_exchangeA | Record a user+assistant exchange from historical or batch imports only. Do NOT use for live conversations — both timestamps are captured at the same instant with no real gap. For live sessions always call log_message twice: once for the user message, once for the assistant response. |
| list_sessionsA | List all audit sessions ordered by most recently active. Returns id, title, ai_tool, message_count, created_at, updated_at. |
| get_session_historyA | Retrieve the full timestamped audit log for a session, oldest first. |
| verify_sessionA | Verify the tamper-evident hash chain for a session. Returns valid=true if no rows were edited after logging, or the first broken link if tampering is detected. |
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 role: starting/resuming sessions, logging messages individually or in batch, listing sessions, retrieving full history, and verifying integrity. No overlaps in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., start_session, list_sessions, verify_session), making the API predictable and easy to navigate.
Six tools cover the essential operations for an audit session manager without redundancy. The count is well-scoped for the server's purpose.
The tool set covers the full lifecycle: session creation, message logging (individual and batch), session listing, history retrieval, and integrity verification. No obvious gaps given the immutability requirement for audit logs.