Chronicle Beta
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retrieve_chunksA | Run Chronicle retrieval for one string query or a list of sub-queries; return standardized chunks with metadata. Supports optional date window and metadata filters. Best practices for the calling LLM:
The returned chunks contain source_name, timestamp, relevance_score, content_raw, content_type, and project fields. The calling LLM should synthesize an evidence-based answer from these chunks, citing sources and presenting an evidence timeline. |
| health_checkA | Light connectivity and status probe. Returns server info, environment flags, and runs a tiny test retrieval to verify the vector store is accessible. |
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 are completely distinct: retrieve_chunks handles data retrieval while health_check verifies connectivity/status. There is no overlap or ambiguity between their purposes.
Both tools follow a clear verb_noun pattern using snake_case (retrieve_chunks, health_check). The naming convention is consistent and predictable.
With only 2 tools, the set feels thin for a full-featured retrieval server, though it covers the core retrieval use case plus a health check. It is borderline but could be expanded.
The retrieval operation is well-covered with filtering and date windows, and health_check provides necessary diagnostics. However, there are no tools for browsing available filters, projects, or content types, which agents might need.