a207-his-mcp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_patient_profileA | 读取患儿档案:人口学、确诊分期、病因、透析方式、过敏史、医生营养上限。 医生助手/风险预警/调度获得全量视图(含 5 天饮食日记与跨月度生化); 营养师视图不含生化;家长视图仅诊断、过敏与上限,且必须携带 guardian_token。 |
| get_diagnosisB | 读取医生确诊的 CKD 分期与透析方式,供营养师与家长助手替代分期复算。 |
| verify_guardian_bindingA | 核验监护人与患儿的绑定关系,家长助手每次访问患儿数据前必经此步。 |
| list_patientsA | 按年龄带/分期/透析方式等条件检索患儿队列,返回 id 列表与摘要。 |
| get_nutrition_ceilingA | 读取医生设定的能量/蛋白/钾/磷/钠/液体上限,作为营养计算与食谱生成的硬约束。 |
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 5 tools
Tools have distinct names and purposes, but get_patient_profile overlaps with get_diagnosis and get_nutrition_ceiling by including diagnosis and nutrition limits in its data. While role-based views and descriptions help clarify intended usage, an agent could be uncertain whether to call the specialized getter or the full profile.
All tools follow a consistent verb_noun pattern with snake_case (get_patient_profile, get_diagnosis, verify_guardian_binding, list_patients, get_nutrition_ceiling). The verbs are predictable (get/list/verify) and resources are clearly named.
Five tools is well-scoped for a patient-data access server focused on read operations and authorization. Each tool serves a distinct function in the workflow, with no redundant or trivial tools.
The server covers core read workflows: patient lookup, detailed profile access, diagnosis verification, nutrition limits, and guardian authorization. Minor gaps exist, such as lacking a separate tool for labs or diet diary, but they are embedded in the profile, so agents can achieve their goals without dead ends.