No user-submitted related servers found.
Scored across 24 tools
Each list_* tool targets a distinct clinical resource (allergies, meds, immunizations, visits, messages, etc.), and the auth tools form a clear sign-in/verify flow, so boundaries are generally crisp. The only mild overlap is mah_get_health_summary versus the individual list tools, which could cause a moment of hesitation about which to call.
Nearly all tools use a consistent mah_ prefix with verb_noun form (list_allergies, get_health_summary, set_active_patient, reply_message). A few deviate slightly with noun-only names like mah_auth_status and mah_healthcheck, but the convention is still highly predictable.
24 tools is on the heavy side, but the domain—a full patient portal with labs, meds, messages, billing, insurance, proxy patients, and multi-step auth—genuinely justifies broad coverage. It stays just under the point where count alone becomes a problem.
The surface covers a wide read-oriented lifecycle: demographics/proxy patients, clinical summaries, results, visits, messages, insurance, and billing, plus auth and diagnostics. Gaps exist around write actions (composing new messages rather than only replying, scheduling, refill requests), but core workflows are supported.