knowledgehub
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kb_searchB | Search indexed knowledge and return traceable document/chunk references. |
| kb_readB | Read one indexed document or a specific indexed chunk. |
| kb_project_contextB | Resolve an absolute project path to its indexed project documentation. |
| kb_statusA | Return KnowledgeHub index health and last scan information. |
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 targets a distinct action: search, read, resolve project context, and check status. There is no functional overlap between them, so an agent can confidently select the right tool.
All tools share the consistent 'kb_' prefix and use snake_case, but two are verb-based (kb_search, kb_read) while two are noun-based (kb_project_context, kb_status). This is a minor deviation from a uniform verb_noun pattern.
With 4 tools, the server is well-scoped for querying a knowledge base. It is not too thin or overloaded, and each tool serves a clear purpose.
The tool set covers the core knowledge access workflows: search, read, get project context, and health status. Missing operations like listing all projects or documents are minor gaps that agents can work around via search.