MCP-Markdown-RAG
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_documentsB | Index Markdown files for semantic search using Milvus. |
| search_documentsA | Search for semantically relevant documents based on query |
| clear_indexA | Clear the vector database's collection and reset the tracking file |
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 3 tools
Each tool performs a distinct function: indexing, searching, and clearing. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (index_documents, search_documents, clear_index), using clear action verbs.
Three tools is well-scoped for a focused RAG server; each tool is essential and covers the core workflow without redundancy.
The set covers indexing, querying, and resetting the vector store. A minor gap is lack of per-document deletion or statistics, but the primary lifecycle is complete.