No user-submitted related servers found.
Scored across 4 tools
Each tool has a clearly distinct role: grep_docs searches file contents, read_doc retrieves exact file ranges, list_docs enumerates the directory structure, and kb_status reports corpus and layer metadata. The tools complement each other with explicit cross-references, so an agent should not confuse them.
Three tools use a predictable verb_noun snake_case pattern (grep_docs, read_doc, list_docs), but doc vs docs is inconsistent and kb_status breaks the verb pattern by using an abbreviation plus noun. The naming is still readable and easy to guess overall.
Four tools is a well-scoped count for a read-only knowledge base MCP: list, grep, read, and status each cover a necessary part of the workflow. There are no redundant tools and no obvious missing core operation.
The tool surface fully covers the read-only domain: agents can discover paths with list_docs, check layer availability with kb_status, locate matches with grep_docs, and retrieve exact citable content with read_doc. Write operations are not part of the stated purpose, so no lifecycle gap exists.