healthcare-ai
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hipaa_ai_assessmentA | Assess HIPAA compliance for AI systems processing Protected Health Information (PHI). Evaluates administrative, physical, and technical safeguards required for AI systems in healthcare settings. |
| fda_ai_assessmentA | Evaluate FDA regulatory requirements for AI/ML-based Software as a Medical Device (SaMD). Determines device classification, regulatory pathway, and compliance requirements per FDA AI/ML Action Plan. |
| clinical_ai_safetyB | Comprehensive clinical AI safety assessment covering bias, validation, human oversight, and EU AI Act obligations for healthcare AI systems. Provides CASA tier recommendation. |
| eu_mdr_complianceA | Assess EU Medical Device Regulation (MDR 2017/745) compliance for AI-based medical devices. Determines MDR classification, conformity assessment route, and regulatory requirements. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| healthcare://regulations/index | |
| healthcare://tools/guide |
TDQS
Scored across 4 tools
Each tool targets a distinct regulatory framework (general AI safety, EU MDR, FDA SaMD, HIPAA), with no overlap in purpose. An agent can easily differentiate them.
Names follow a pattern of domain/regulation plus topic, but vary between 'safety', 'compliance', and 'assessment' (e.g., clinical_ai_safety vs. eu_mdr_compliance vs. fda_ai_assessment). Slight inconsistency but still clear and predictable.
Four tools is well-scoped for a healthcare AI compliance server, covering major regulations without excess. Each tool serves a necessary role.
Covers core regulatory areas (safety, EU MDR, FDA, HIPAA), but misses some potentially relevant frameworks like GDPR or ISO standards. Minor gaps that don't severely hinder the agent.