Keepygaga RAG
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEEPYGAGA_RAG_CONFIG | No | Path to the configuration file (runtime override). | |
| KEEPYGAGA_RAG_DASHBOARD_PORT | No | Port for the dashboard (runtime override). Defaults to 8765. | |
| KEEPYGAGA_RAG_DASHBOARD_AUTO_CLOSE | No | Whether to automatically close the dashboard (runtime override). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search ordinary local knowledge with hybrid FTS and vector recall, reciprocal rank fusion, and online reranking. Results are grouped by text table and include source paths, headings, chunk text, and scores. This tool never searches core Agent memory or context-backup trees, even when either appears below a configured source root. Indexing text is sent to the configured Embedding provider; query text and candidate chunks are sent to the configured Reranker provider only for sources with current user consent. Args: query: Natural-language or exact-text knowledge query. top_k: Results to return, from 1 through 20. table_ids: Optional text-table filters, at most 20. source_ids: Optional source filters, at most 20. Results locate candidate source material. Read the returned source file before treating a match as authoritative. |
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 exposed, there is no possible overlap or misselection between tools. The single search operation is unambiguous.
The lone tool is named with a clear, lowercase verb ('search') that accurately describes its action. There are no other names to create mixed conventions or inconsistent patterns.
A single tool is borderline: acceptable for a retrieval-only endpoint, but thin for a server branded as a RAG system, which would typically benefit from source/table discovery or management tools.
The search tool itself is feature-rich with hybrid retrieval, reranking, and filters, but the surface is incomplete for a RAG lifecycle: agents cannot ingest, update, delete, or even enumerate available sources/tables without external knowledge.