cumcm-rag-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CUMCM_RAG_ROOT | Yes | Path to the project or data root directory containing config/rag.yaml and data/manifest. Required for normal installations or when running from outside the repository. |
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 |
|---|---|
| rag_searchB | 检索国赛优化与决策类公开语料；可按题号、层级和文档类型过滤。 |
| rag_get_case_contextC | 按题号取得案例卡与通用方法卡组成的上下文。 |
| rag_get_documentB | 读取 manifest 已登记的文本型公开语料，拒绝未登记路径。 |
| rag_list_sourcesC | 列出 manifest 中的来源、许可、层级、题号、URL 与哈希。 |
| rag_get_statusA | 返回语料、manifest 与本地生成索引的状态。 |
| rag_healthB | 检查路径与索引；deep=true 时额外执行真实检索探针。 |
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 6 tools
Most tools have clearly distinct roles: search, document retrieval, source listing, and case-context assembly are well separated. However, rag_get_status and rag_health overlap in purpose, both probing system/index health, which could cause occasional misselection.
All tools share the rag_ prefix and use consistent snake_case with action-oriented verbs like get, search, list, and health. The naming pattern is predictable and easy to extend.
Six tools form a tight, well-scoped surface for a RAG retrieval server: search, document access, source metadata, context assembly, and health/status checks. No tool feels redundant or unnecessary.
The retrieval side is well covered: search, document reading, source listing, case context, and health checks. Minor gaps exist around index management or ingestion, but the apparent read-only RAG purpose is largely satisfied.