KnowS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWS_API_KEY | Yes | KnowS API 密钥 | |
| KNOWS_API_HOST | No | API 地址，默认 https://dev-api.nullht.com | https://dev-api.nullht.com |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ai_searchC | AI 检索：用户提问，返回与该问题相关的医学证据列表 |
| evidence_summaryB | 对单篇证据进行 AI 概要总结 |
| all_evidence_summaryA | 获取所有证据的单篇 AI 总结（收集完整的流式响应后返回） |
| evidence_highlightB | 返回单篇证据被引用的原文部分（高亮内容） |
| answerB | 基于问题和检索出来的证据，生成场景总结（非流式） |
| answer_streamC | 基于问题和检索出来的证据，生成场景总结（收集完整的流式响应后返回） |
| auto_taggingC | 对证据进行自动化标签提取（如研究类型、疾病领域、样本量等） |
| get_paper_enA | 获取英文文献的详细信息（标题、摘要、影响因子、分区等） |
| get_paper_cnC | 获取中文文献的详细信息 |
| get_guideC | 获取医学指南的详细信息 |
| get_meetingC | 获取医学会议记录的详细信息 |
| list_questionsC | 获取用户的历史提问列表，支持时间范围和分页 |
| list_interpretationsC | 获取用户的单篇文献 AI 解读历史记录，支持时间范围和分页 |
| create_evidence_by_pdfB | 通过上传 PDF 文件创建新的证据 |
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 14 tools
Most tools have distinct purposes (e.g., ai_search vs. answer vs. evidence_summary). However, answer and answer_stream are clearly variants of the same operation, and all_evidence_summary and evidence_summary overlap in scope, causing slight ambiguity.
Naming patterns are mixed: some tools use verb_noun (get_guide, list_questions) while others use noun_verb or noun_noun (evidence_highlight, ai_search). The presence of answer and answer_stream as single verbs breaks the pattern, reducing consistency.
With 14 tools covering search, summarization, evidence management, and history, the count feels well-scoped for a medical knowledge server. Each tool serves a clear role without unnecessary redundancy.
The tool set covers core workflows like searching, answering, and summarizing, but lacks update/delete operations for evidence and does not provide listing tools for guides or meetings, leaving notable gaps in lifecycle coverage.