DrugWise
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orchestrator_check_drug_interactionsA | Checks real-time drug interaction safety by querying FDA adverse event reports, PubMed biomedical research, and ClinicalTrials.gov simultaneously. Call this when a doctor wants to prescribe a new drug to a patient already on other medications. Returns live evidence from all three sources with dates, so you know the data is current. Always call get_drug_info first to understand the mechanism, then call this tool. |
| drug_info_get_drug_infoA | Get comprehensive pharmacological information about any drug — drug class, enzyme pathways it inhibits or induces (CYP2C9, CYP3A4, etc.), brand names, generic name, primary use, and which other drug classes it commonly interacts with. ALWAYS call this tool first before calling check_drug_interactions. Understanding the mechanism (e.g. strong CYP2C9 inhibitor) tells you which patient medications to be most concerned about. |
| drug_alternatives_get_drug_alternativesA | When a dangerous drug interaction is found, call this tool to get safer alternative medications in the same therapeutic class. Returns brand names, generic names, key side effects, contraindications, and why the alternative is safer for this specific patient. Provide the drug class and the condition being treated for best results. |
| clinical_trials_search_clinical_trialsC | Search ClinicalTrials.gov for studies related to a drug and current medications. |
| polypharmacy_risk_check_polypharmacy_riskC | Checks every pair of medications in a patient medication list for interaction risks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| clinical_safety_check | Activates clinical pharmacologist reasoning mode for drug interaction evaluation. Use this prompt to begin any drug safety consultation. |
| polypharmacy_audit | Activates a full medication audit mode for patients on multiple drugs. Use when onboarding a new patient or auditing an existing medication regimen before adding anything new. |
| interaction_report | Generates a structured, shareable interaction report from retrieved evidence. Use after check_drug_interactions has returned data. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| patient_profile | Current patient clinical context including full medication list, age, existing conditions, and organ function status. The agent reads this before making tool calls to ensure all drug checks are relevant to this specific patient. |
| demo_patient | Pre-loaded demo patient for hackathon demonstration — 72-year-old with atrial fibrillation on warfarin, lisinopril, and metformin |
| Health Checks | Current health status of all registered health checks |
| Drug Checker | UI component for Drug Checker |
| Patient Profile | UI component for Patient Profile |
| Widget Examples | Provides metadata and examples for all registered UI widgets |
TDQS
Scored across 5 tools
Tools have distinct purposes, but there is some overlap: orchestrator_check_drug_interactions already queries ClinicalTrials.gov, overlapping with clinical_trials_search_clinical_trials. Also, polypharmacy_risk_check_polypharmacy_risk duplicates the interaction checking logic for multiple medications. Descriptions help differentiate, but boundaries are not perfectly clear.
Naming uses long descriptive underscores, but prefixes are inconsistent: 'orchestrator_', 'drug_info_', 'drug_alternatives_', 'clinical_trials_', 'polypharmacy_risk_'. Also, 'clinical_trials_search_clinical_trials' is redundant. Overall, pattern is present but mixed.
With 5 tools, the server is well-scoped for its purpose. Each tool covers an essential step in the drug interaction workflow. Could potentially be consolidated (e.g., search trials into check interactions), but current count is reasonable.
Covers core workflow: get info, check interactions, find alternatives, search trials, polypharmacy check. Missing drug-food interactions and allergy checks, but these are tangential. Minor gaps, but agents can still complete main tasks.