Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@dayi-search-mcp 查找高血压的疾病信息"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
基于中国医药信息查询平台（Dayi）的检索与提取项目。
当前已形成首个正式可用版本：@xiaoyibao_2025/dayi-mcp-server@0.1.7。
modelscope https://modelscope.cn/mcp/servers/caiql2002/dayi-search-mcp
Python Core（src/dayi_core）
负责检索、详情提取、结构化输出
支持类型：medical / disease / doctor / symptom
MCP Server（mcp-server）
Node/TypeScript 实现
已打包内置 Python Core（发布包内 python/dayi_core）
Related MCP server: Query Table MCP Server
PYTHONPATH=src python3 -m dayi_core.cli.main query --type medical --keyword 替吉奥 --json /tmp/替吉奥.jsondayi_query：指定 type + keyword 查询
dayi_query_auto：自动判定类型
medical 输出增强：
record.sections.药品详情：成分/性状/适应症/用法用量/规格/贮藏方法/有效期/执行标准
record.sections.注意事项：不良反应/禁忌/药物相互作用/注意事项
返回 structuredContent.raw 原始证据：
detail_html / nuxt_script / search_payload
支持落盘：
save_path 可选
不传时默认落盘 /tmp/标题_YYYYMMDD.json
返回 structuredContent.saved_path
使用 mcpServers 配置（推荐锁版本）：
{
"mcpServers": {
"dayi-mcp-server": {
"command": "npx",
"args": ["-y", "@xiaoyibao_2025/dayi-mcp-server@0.1.7"],
"transport": "stdio"
}
}
}在 MCP/工具接入里新增 stdio server，命令填：
npx -y @xiaoyibao_2025/dayi-mcp-server@0.1.7transport 选 stdio，工具自动通过 tools/list 发现。
在插件或运行时的 MCP 配置中添加一个 stdio server：
{
"mcpServers": {
"dayi-mcp-server": {
"command": "npx",
"args": ["-y", "@xiaoyibao_2025/dayi-mcp-server@0.1.7"],
"transport": "stdio"
}
}
}在项目的 MCP 配置文件中注册：
{
"mcpServers": {
"dayi-mcp-server": {
"command": "npx",
"args": ["-y", "@xiaoyibao_2025/dayi-mcp-server@0.1.7"],
"transport": "stdio"
}
}
}使用同样的 stdio MCP 配置方式，命令保持一致：
npx -y @xiaoyibao_2025/dayi-mcp-server@0.1.7# Python tests
pytest tests -q
# MCP build
cd mcp-server
npm install
npm run sync:python
npm run build已新增项目内技能：
skills/dayi-mcp-query/SKILL.md
用途：在支持 Skill 机制的客户端中，自动触发 Dayi MCP 查询流程（药品/疾病/医生/症状、落盘 JSON、RAG 入库预处理）。
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | ||
| keyword | Yes | ||
| save_path | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | Yes | ||
| type_hint | No | ||
| save_path | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0dayi_querydayi_query_autoBoth tools have no descriptions and nearly identical names (dayi_query vs dayi_query_auto), making them indistinguishable for an agent.
Names follow a consistent prefix 'dayi_query' but one has a suffix '_auto', creating ambiguity. The pattern is present but unclear.
Only two tools are provided for a search service, which likely requires more operations like filtering, pagination, or results management.
Without descriptions, it's unclear what the tools do, but having only two query-like tools suggests significant gaps in search functionality.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Search Chinese books with Douban ratings, AI book guides and curated toplists. Free, no API key.
Medical RAG: semantic search for clinical guidelines, drug interactions, diagnoses & EHR data.
Medical RAG: semantic search for clinical guidelines, drug interactions, diagnoses & EHR data.
Turn messy text into strict JSON schemas agents can trust (invoice, receipt, contact, resume).
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/PancrePal-xiaoyibao/dayi-search-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
