manual-rag
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_DIR | No | Absolute path to the data directory, overriding the default data location. | |
| OLLAMA_HOST | No | Ollama host URL, overridable via environment variable. | |
| EMBEDDING_MODEL | No | Embedding model to use, overridable via environment variable (default is nomic-embed-text). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_manualA | Search the indexed reference manuals for information. Call get_sources first to learn which manuals are indexed and what each covers. Then search a manual whenever the user asks about a feature, workflow, keyboard shortcut, setting, or concept covered by one of those manuals — this is the authoritative source, prefer it over guessing or a web search. Pass the optional "source" parameter to restrict results to a single manual (use the exact source id returned by get_sources):
The tool returns relevant excerpts with page numbers, chapter information, source identification, and a relevance score. |
| get_sourcesA | Get a list of all indexed reference manuals with their chunk counts, page ranges, and detected chapters. Use this tool when the user wants to:
|
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
search_manual and get_sources have clearly distinct purposes: one retrieves content from manuals, the other lists available sources and their structure. There is no overlap or ambiguity between them.
Both tools follow a consistent snake_case verb_noun pattern (search_manual, get_sources). The naming is predictable and readable.
Only 2 tools are provided, which is on the thin side for a RAG server. While both are essential and well-scoped, the count is borderline minimal.
The core workflow of listing sources and searching across or within manuals is covered. However, there is no direct way to retrieve full documents or specific pages beyond search excerpts, which is a minor gap.