Hospital Data MCP Server
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wxoGetVitalSignsInformationA | Returns patient vital signs from the bedside system (Blood pressure, pulse, creatine data, bmi, weight, height) or None. |
| wxoGetPatientInformationA | Returns basic patient information from the healthcare database including personal details, contact information and insurance data or None. |
| wxoGetMedicalInformationC | Returns comprehensive patient medical inforamation regarding the diagnosis (condition), allergies and any given prescriptions or None |
| wxoGetDrugInformationC | Returns comprehensive drug medical inforamation for a given drug or None |
| wxoGetDrugInterationsB | Returns comprehensive drug interaction medical inforamation for two given drugs or None |
| wxoGetDrugContraindicationsB | Returns comprehensive drug contraindication medical inforamation for a given drug or None |
| wxoGetDrugAlternativeTreatmentsC | Retrieves information about alternative treatments for a given drug or None |
| wxoGetPatient360A | Given a patient id, construct a 360 view of a patient, their information, medical data and most recent vital signs |
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 8 tools
Most tools target distinct data types (drug info, vital signs, patient info, medical info). The only overlap is wxoGetPatient360, which explicitly aggregates the individual patient-related getters, but its purpose as a composite view is clear from the description.
All tools follow the exact same 'wxoGet' + PascalCase noun pattern, creating a predictable and uniform naming convention. The minor typo in 'DrugInterations' does not affect the consistent structure.
With 8 tools, the server is well-scoped for a hospital data access API. The number is within the ideal 3-15 range and each tool serves a clear query purpose.
The tool set covers core patient, medical, vital signs, and drug-related queries, but lacks search/list operations (e.g., find patients, search drugs) and any write capabilities. While likely read-only, the absence of basic lookup endpoints creates notable gaps for general hospital data exploration.