Knowledge Master
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Semantic search across the knowledge base. Returns relevant chunks with source info and graph context (author, repo, related docs). |
| index_repoB | Index a git repository into the knowledge graph. Parses code files, extracts authors, builds relationships. |
| index_directoryB | Index markdown/text files from a directory. |
| get_statusA | Get knowledge base statistics: number of chunks, documents, repos indexed. |
| blast_radiusA | Show what depends on a target (service, tech, or file). Returns all entities that would be affected by changing the target. |
| check_conventionsB | Check if a repo or path follows the detected coding conventions (naming, structure, patterns). Returns pass/fail for each convention. |
| safe_to_changeC | Assess risk of changing a target. Returns risk level, blast radius, and test coverage. |
| who_ownsB | Find who owns a file based on OWNS relationships in the graph. |
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 8 tools
Each tool has a clearly distinct purpose: indexing, searching, impact analysis, ownership, conventions checking. Even similar tools like blast_radius and safe_to_change are differentiated by depth of analysis.
Tools use snake_case consistently. Most follow verb_noun pattern (index_directory, check_conventions), but some are noun-based (blast_radius, safe_to_change). Still predictable and readable.
8 tools is well-scoped for a knowledge management server. Each tool covers a core function without redundancy or bloat.
Covers indexing, search, impact analysis, conventions checking, and ownership. Missing delete or update operations for indexed data, but core read-oriented workflows are complete.