Skip to main content
Glama
ikungsjl

MCP Knowledge Base Server

by ikungsjl

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
add_documentC

添加单个文档到知识库

add_directoryC

添加目录中的所有文档到知识库

query_knowledge_baseD

查询知识库

list_documentsB

列出知识库中的所有文档

get_documentC

获取特定文档信息

remove_documentC

从知识库中移除文档

clear_knowledge_baseD

清空知识库

get_statsC

获取知识库统计信息

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 8 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific action on the knowledge base (add, clear, get, list, query, remove) with clear boundaries between operations like adding documents versus querying versus management functions.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., add_document, list_documents, query_knowledge_base). The naming is predictable and readable without any deviations in style or convention.

Tool Count5/5

With 8 tools, this server is well-scoped for a knowledge base management system. Each tool earns its place by covering essential CRUD operations, querying, and administrative functions without being overly sparse or bloated.

Completeness5/5

The tool set provides complete CRUD/lifecycle coverage for the knowledge base domain. It includes creation (add_document, add_directory), retrieval (get_document, list_documents, query_knowledge_base), deletion (remove_document, clear_knowledge_base), and monitoring (get_stats), with no obvious gaps or dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues