kb-assistant
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledge_baseA | Hybrid search (BM25 + embeddings + reranker) over indexed repository docs and code. Use for any question about how our code or documentation works. Returns the top-k chunks with path, line range, a GitHub permalink and the chunk text. Write the query the way the answer would be phrased, and include exact identifiers (function, class, config key names) when you know them. |
| read_fileA | Read an indexed file (or a line range of it) by repository-relative path. Use after search_knowledge_base to see surrounding context. Only files in the index that you have permission to read are available. |
| ask_knowledge_baseA | Answer a question end-to-end with citations, grounded only in indexed sources. Returns |
| list_sourcesA | List indexed repositories, pinned commits and index statistics. |
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 4 tools
read_file and list_sources are clearly distinct from the query tools. search_knowledge_base and ask_knowledge_base both accept question-style queries about the same corpus, which introduces mild overlap, but their descriptions clearly separate raw-chunk retrieval from a synthesized cited answer.
All four tools use snake_case and follow a consistent verb_noun pattern: list_sources, search_knowledge_base, read_file, ask_knowledge_base. No stylistic deviations.
Four tools is a tight, well-scoped set for a read-only knowledge base assistant: enumerate sources, search, read context, and ask. Each tool earns its place without redundancy or bloat.
The read-only RAG lifecycle is well covered (list sources, search, fetch file context, answer with citations), and ask_knowledge_base handles the 'no answer' case gracefully. Minor gaps like listing files within a repo or fetch-by-permalink are workable around via search/read_file.