chronomem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHRONOMEM_DB | Yes | Path to the SQLite database file used by ChronoMem. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chronomem_rememberB | Store a durable fact in bi-temporal memory. Supports automatic entity resolution and superseding previous beliefs. |
| chronomem_recallA | Retrieve relevant facts for a query using 4-Way Reciprocal Rank Fusion, strictly packed within a token budget. |
| chronomem_supersedeA | Replace an outdated fact with new accurate information, establishing an audit lineage. |
| chronomem_forgetB | Expire/invalidate a fact so it is no longer retrieved, while preserving historical audit logs. |
| chronomem_timelineB | Trace how beliefs and facts about a specific entity have changed over time. |
| chronomem_contradictionsC | Find active facts that potentially contradict each other. |
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
Most tools have clear distinct purposes, but remember can automatically supersede prior beliefs, creating some overlap with supersede. forget and supersede also both invalidate old facts, though their descriptions distinguish replacement from expiration.
All tools use the chronomem_ prefix and snake_case, but the core names mix verbs (remember, recall, supersede, forget) with nouns (timeline, contradictions). This is a minor deviation from a purely predictable verb_noun pattern.
Six tools is well-scoped for a bi-temporal memory server, covering core lifecycle operations without bloat. Each tool appears to earn its place.
The surface covers create, query, update/replace, expire, historical tracing, and contradiction detection. This is a complete lifecycle for the stated memory-management domain, with no obvious dead ends.