a207-followup-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 |
|---|---|
| schedule_followupA | 创建随访计划（写，MX 收口：仅医生/营养师/编排层）。频率按 KDIGO 2024 儿科推荐自动计算。 ckd_stage=G1/G2/G3a/G3b/G4/G5/G5D；anchor_date=本次就诊日 YYYY-MM-DD；plan_summary 摘要所有角色可见； note_to_clinician 仅医生/营养可见。返回含 next_due_date 的计划。 |
| get_followup_recordsA | 读取随访记录与计划时间线（读，所有角色可读）。 临床角色（医生/营养/编排/风险）看完整记录（含原始医生备注）；患者/家属角色仅见摘要——医生备注被剔除。 |
| get_adherence_scoreA | 计算并记录依从性评分（M4 拥有依从性数据）。diet/med/visit 三域比率(0-1) → 加权复合分(0-100)。 等级：≥80 好 / 50-79 中 / <50 差。默认等权（饮食/用药/就诊各 1/3，待临床验证）。 |
| get_pew_historyB | PEW 历史聚合 facade（ADR-007：存储归属 M3）。 接受 M3 get_pew_history 的输出（list of {date, score, level}），并入统一随访时间线。零跨包 import。 |
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 4 tools
Each tool targets a distinct function: scheduling, reading records, computing adherence, and retrieving PEW history. There is slight potential confusion between get_followup_records and get_pew_history since both are reads related to the timeline, but the descriptions clarify their specific scopes.
All tool names follow a consistent verb_noun snake_case pattern (schedule_followup, get_followup_records, get_adherence_score, get_pew_history). The 'get_' prefix is uniformly used for read operations, with no mixed conventions or camelCase deviations.
Four tools cover the core follow-up workflow—creating plans, reading records, scoring adherence, and aggregating PEW data. This is well-scoped for the server's purpose and falls within the ideal 3-15 range.
The server supports creating and reading follow-up plans/records but lacks update/delete operations for plans, which are common lifecycle needs. It also has no tool to record completed follow-ups, leaving notable gaps in the follow-up management cycle.