Chilon Recall
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAG_API_KEY | Yes | API key for the embedding provider (and possibly reranking if it uses the same key). | |
| RAG_MANAGER_CONFIG | Yes | Path to the chilon-recall JSON configuration file. | |
| RAG_RERANK_API_KEY | No | Optional API key for the reranking provider. Required only if reranking is enabled in the configuration. | |
| CHILON_RECALL_PYTHON | Yes | Path to the Python interpreter (Python 3.10+) used by the retrieval engine. |
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 |
|---|---|
| rag_statusA | Inspect source coverage, provider readiness, and the active index without changing data. |
| rag_list_documentsA | List text documents included by the fixed knowledge-base configuration. |
| rag_save_configB | Atomically update approved non-secret settings in the server's fixed configuration file. |
| rag_buildA | Preview or execute a staged index build. Execution requires the unexpired token returned by preview. |
| rag_syncA | Preview or execute a staged content-hash sync. Unchanged files reuse existing vectors; added, modified, and deleted files are reconciled safely. |
| rag_queryB | Retrieve source-backed passages from the active local index. |
| rag_clear_indexA | Preview or move the active index into a recoverable backup. Execution requires a matching token. |
| rag_list_backupsA | List recoverable index backups without exposing their absolute paths. |
| rag_restore_indexA | Preview or restore a named backup. Execution requires a matching token and backs up the current index first. |
| textbook_qaC | Retrieve evidence for answering a learning question from the configured knowledge base. |
| concept_compareC | Retrieve evidence for comparing two concepts across clear dimensions. |
| chapter_summaryC | Retrieve evidence for a structured chapter or topic summary. |
| review_outlineC | Retrieve evidence and organize it for focused study or review. |
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 13 tools
The tools split into RAG lifecycle operations and study-retrieval modes, each with distinct purposes. rag_sync and rag_build are the closest pair, but their descriptions differentiate incremental reconciliation from full index build, so an agent can usually pick correctly.
All names use snake_case and the rag_ prefix clearly groups administration tools, but the study helpers follow a noun-phrase style rather than the verb_noun convention. The one outlier is rag_status, which uses a noun where an action verb would be more consistent.
Thirteen tools is within the well-scoped range, and each tool has a non-redundant role: nine cover the RAG index lifecycle and four cover retrieval/study modes. No tool feels like filler.
The RAG lifecycle is covered end-to-end: build, sync, query, status, config, clear/backup, list backups, and restore. The study side has compare, summary, outline, and Q&A retrieval, so the server supports its apparent purpose without obvious dead ends.