ChronoGuard
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chronoguard_resolve_timeB | Deterministic temporal resolution and business-date arithmetic. Use for current time, elapsed or calendar offsets, rolling spans, business-day offsets, SLAs, and financial cutoffs. v0.1 business-day calendars assume a Saturday/Sunday weekend. |
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 1 tool
With only one tool, there is no possibility of overlap or misselection. The single tool has a clearly stated purpose (deterministic temporal resolution and business-date arithmetic).
The lone name follows a clean snake_case server-prefixed convention (chronoguard_resolve_time). No mixing of styles is possible, so consistency is trivially satisfied.
A single tool for an entire temporal domain is borderline thin; a server covering current time, offsets, spans, business days, and SLAs could reasonably expose separate operations. It is not trivial, so it is not an extreme mismatch, but the surface is minimal.
The tool claims broad coverage (current time, elapsed/calendar offsets, rolling spans, business-day offsets, SLAs, financial cutoffs), but notable gaps remain: no timezone conversion, no date parsing/formatting, and business-day calendars are hardcoded to Sat/Sun weekends with no holiday calendar support.