Knowledge Retrieval Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-documentsC | Search documents using BM25 algorithm. Takes keyword arrays and returns relevant document chunks. |
| get-document-by-idC | Retrieve full document by ID. |
| list-domainsB | List all available domains and their document counts. |
| get-chunk-with-contextC | Get specific chunk with surrounding context. |
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
Each tool has a clearly distinct purpose with no overlap: get-chunk-with-context retrieves specific text segments, get-document-by-id fetches entire documents, list-domains provides metadata, and search-documents performs keyword-based searches. The descriptions reinforce these unique functions, eliminating any ambiguity.
The tools follow a consistent verb_noun pattern (e.g., get-chunk-with-context, get-document-by-id, list-domains, search-documents), with all using hyphens for readability. The minor deviation is that 'get-chunk-with-context' includes a prepositional phrase, but overall naming remains predictable and clear.
With 4 tools, the server is well-scoped for knowledge retrieval, covering core operations like listing domains, retrieving documents/chunks, and searching. This count is efficient and avoids bloat, with each tool serving a distinct and necessary function in the domain.
The tool set covers essential retrieval workflows: metadata listing, full document access, chunk retrieval, and search. A minor gap is the lack of update or delete operations, but this aligns with a retrieval-focused server, and agents can work effectively with the provided read-only tools.