Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
calculate_clinical_scoreA

Executes validated mathematical clinical risk calculators, renal clearance formulas, triage indices, and patient-specific dosage adjustments with ceiling caps using deterministic arithmetic.

When to use:

  • Calculating exact, non-hallucinated clinical risk scores, renal staging, physiological indices, or patient-specific dosage adjustments from discrete patient parameters.

When NOT to use:

  • Acute emergency triage or symptom-based red-flag evaluation without discrete parameters (use check_red_flags instead).

  • Drug-drug interaction or pharmacological contraindication screening (use check_drug_interactions instead).

  • Mapping commercial trade brand names to generic entities (use normalize_terminology instead).

Parameter constraints & formats:

  • 'calculator_id': Target calculation engine enum from inputSchema.

  • 'params': Inputs mapped by clinical calculator domain:

    • Renal clearance ('ckd_epi_2021_egfr', 'bedside_schwartz_egfr', 'cockcroft_gault_crcl'): serum_creatinine, age_years (>=18 for adult, <18 for Schwartz), biological_sex, actual_weight_kg, height_cm (evaluates KDIGO 2021 and Schwartz equations).

    • Cardiovascular & bleeding ('cha2ds2_va_esc2024', 'cha2ds2_vasc_aha2023', 'has_bled_score'): age_years, biological_sex, and medical history booleans evaluating ESC 2024 and HAS-BLED thresholds.

    • Acuity & pneumonia triage ('news2_score', 'curb65_score'): respiratory_rate, oxygen_saturation, systolic_bp, pulse_rate, temperature_celsius, consciousness_level ('Alert'|'CVPU'), on_supplemental_oxygen, confusion, BUN.

    • Pediatric dosing & BSA ('pediatric_dose_calculator', 'mosteller_bsa'): weight_kg, height_cm, dose_per_kg, max_single_adult_dose_mg (enforcing adult ceiling caps to prevent pediatric overdosing).

    • Thromboembolism criteria ('wells_dvt_score', 'wells_pe_score'): clinical criteria booleans evaluating pre-test probability for DVT and pulmonary embolism.

Behavioral guarantees & return states:

  • Pure deterministic arithmetic: Stateless in-memory execution; requires no API keys, credentials, or network auth, with zero rate limits.

  • Physiological boundary validation: Parameters exceeding safe physiological limits trigger SafeCalculationRefusal (status='CALCULATION_REFUSED_SAFE_ABSTENTION') with clinical reason; unrecognized calculator_id safely returns an explicit error message without throwing uncaught exceptions.

  • Output contract: Returns structured JSON with calculator_id, score, unit, interpretation_band, clinical_recommendation, guideline_citation, and warnings.

check_red_flagsA

Evaluates a patient clinical consultation envelope against multi-layered safety guardrails, detecting acute life-threatening emergencies, critical drug-drug interactions, inter-skill treatment conflicts, and missing mandatory data.

When to use:

  • Screening clinical consultation envelopes for acute medical emergencies, vital sign decompensation, red flags, or contraindicated treatment plans.

When NOT to use:

  • Computing specific numerical clinical risk scores like CHA2DS2-VA or eGFR (use calculate_clinical_score instead).

  • Screening isolated medication lists without patient context (use check_drug_interactions instead).

  • Redacting patient identifiers or personal health information (use scrub_phi instead).

  • Managing longitudinal patient records or EHR persistence (use external FHIR/EHR systems instead).

Parameter constraints & formats:

  • 'envelope': Consultation payload structured as:

    • patient_id: Anonymized audit tracking ID (e.g. 'PT-8921').

    • demographics: Evaluates age-stratified risks, biological sex, and pregnancy contraindications.

    • observations: Presenting symptoms scanned for acute emergency triggers.

    • active_medications: Current medications evaluated for critical co-prescribing DDIs.

    • vital_signs: Screened against clinical shock, sepsis, and vital decompensation thresholds.

    • proposed_plan: Proposed intervention cross-checked against clinical contraindications.

Behavioral guarantees & return states:

  • Deterministic evaluation pipeline sequentially checking acute emergencies, critical DDIs, missing data, and treatment conflicts.

  • Auth & limits: Fully local execution; requires no API keys, credentials, or network auth, with zero rate limits.

  • Verdict outcomes: gate_status returns 'PASSED_PROCEED', 'SAFE_ABSTENTION_EMERGENCY_ESCALATION' (with immediate emergency redirection and contacts), or 'SAFE_ABSTENTION_DATA_DEFICIT'. Missing vitals safely trigger data deficit status without throwing uncaught exceptions.

check_drug_interactionsA

Screens patient medication regimens for critical, contraindicated, or fatal drug-drug interactions (DDIs), automatically resolves regional trade brand names to generic INN entities, and evaluates demographic contraindications (pregnancy, pediatric, geriatric).

When to use:

  • Evaluating prescription combinations or medication lists for dangerous interactions, QT prolongation, bleeding risks, or pregnancy contraindications.

When NOT to use:

  • Comprehensive clinical consultation triage with vital signs and symptom red flags (use check_red_flags instead).

  • Translating single brand names without DDI screening (use normalize_terminology instead).

  • Renal dosage adjustment or clinical clearance calculations (use calculate_clinical_score instead).

Parameter constraints & formats:

  • 'medications': Trade brand or generic medication names (e.g. ['Concor 5mg', 'Voltaren 75mg', 'Warfarin 5mg']).

  • 'patient_demographics':

    • age_years (0-120): Evaluates Beers Criteria geriatric (>65) and pediatric (<18) contraindications.

    • biological_sex: Sex-linked pharmacological risks ('male'|'female').

    • pregnancy_status: 'not_pregnant' (default), 'PREGNANT' (suspected), 'CONFIRMED_PREGNANT' (enforces strict FDA Category X blocks), or specific trimester ('first_trimester' to 'third_trimester').

Behavioral guarantees & return states:

  • Deterministic pharmacological rule engine grounded in curated interaction databases; stateless with zero external network calls or patient storage.

  • Auth & limits: Fully local execution; requires no API keys, credentials, or network auth, with zero rate limits.

  • Severity stratification: Interactions are categorized as 'CONTRAINDICATED' (fatal or severe co-administration hazard), 'MAJOR' (serious risk requiring intervention), or 'MODERATE' (monitoring recommended), each paired with safe therapeutic alternatives.

  • Error handling: Clean regimens return interactions_found_count=0; unrecognized brand names are reported in warnings without throwing exceptions.

verify_evidenceA

Performs two-stage medical evidence verification: validates bibliographic citation existence and DOI authenticity, and verifies clinical claim entailment against authoritative guideline corpora with GRADE certainty scoring.

When to use:

  • Verifying whether a clinical assertion, guideline claim, or medical literature citation is authentic, guideline-concordant, and free of medical hallucination.

When NOT to use:

  • Executing mathematical clinical calculators or risk algorithms (use calculate_clinical_score instead).

  • Triage screening of patient acute emergency symptoms or vital signs (use check_red_flags instead).

  • Redacting patient identifying data from clinical records (use scrub_phi instead).

Parameter constraints & formats:

  • 'ref_id': Standardized guideline registry key formatted as '[ORGANIZATION][YEAR][TOPIC]' (e.g. 'ESC_2024_AF' for ESC atrial fibrillation, 'KDIGO_2021' for chronic kidney disease, 'AHA_2023_HF' for heart failure, 'BTS_2023_PNEUMONIA' for British Thoracic Society); cross-verified against curated bibliographic registry.

  • 'claim': Natural language clinical statement, diagnostic assertion, or therapeutic recommendation (e.g. 'Oral anticoagulation is recommended for male patients with non-valvular AF and CHA2DS2-VA score >= 2'); parsed for entities, comparator thresholds, and direction of effect against source guideline text.

  • 'patient_age_years': Patient age in years to evaluate age-stratified guideline applicability (e.g. pediatric <18 cutoffs in Schwartz vs adult >=18 in CKD-EPI); omitted evaluates general adult population.

  • 'patient_is_pregnant': Flag indicating pregnancy status to activate teratogenicity checks and maternal-fetal clinical guideline boundaries.

Behavioral guarantees & return states:

  • Pure deterministic offline cross-verification; executes in memory without network telemetry or data persistence.

  • Auth & limits: Fully local execution; requires no API keys, credentials, or network auth, with zero rate limits.

  • Return contract: Returns citation_metadata (ref_id, validity boolean, DOI, publication year) and claim_entailment (status 'SUPPORTED'|'REFUTED'|'UNVERIFIED', confidence 0.0-1.0, and GRADE certainty 'HIGH'|'MODERATE'|'LOW'|'VERY_LOW').

  • Error handling: Unrecognized ref_id or unverified citation safely returns valid=false and status='UNVERIFIED' without throwing uncaught exceptions.

scrub_phiA

Scans clinical narratives and de-identifies Protected Health Information (PHI), masking HIPAA Safe Harbor 18 identifiers, Egyptian National IDs (14 digits), Saudi Iqama/National IDs (10 digits), Medical Record Numbers (MRN), phone numbers, and email addresses.

When to use:

  • Sanitizing patient narratives, consultation transcripts, or discharge summaries before logging, exporting, or passing to external models or public registries.

When NOT to use:

  • Detecting adversarial prompt injections, jailbreaks, or security exploits (use scan_prompt_security instead).

  • Calculating clinical risk scores or physiological parameters (use calculate_clinical_score or check_red_flags instead).

  • Normalizing pharmaceutical brand names to generic entities (use normalize_terminology instead).

Parameter constraints & formats:

  • 'text': Unstructured clinical narrative, progress note, or dialogue string (up to 500,000 characters) containing patient identifiers to mask.

Behavioral guarantees & return states:

  • Non-LLM deterministic transformation running locally in memory using regex and Luhn checksum validation; requires no external APIs, credentials, or rate limits.

  • Token substitution: Direct identifiers are replaced with standardized masking tokens ([NATIONAL_ID_REDACTED], [PHONE_REDACTED], [EMAIL_REDACTED], [MRN_REDACTED]) while preserving clinical timeline and context.

  • Return contract: Returns scrubbed_text alongside audit_report (total_entities_detected and breakdown by type); stateless with zero disk logging or network leakage.

scan_prompt_securityA

Analyzes untrusted user inputs, clinical prompts, or external dialogue for adversarial attacks, prompt injections, system jailbreaks, role-play overrides, and clinical guardrail bypass attempts.

When to use:

  • Sanitizing and vetting untrusted input strings from patients, clinicians, or third-party integrations before processing by downstream LLM reasoning agents.

When NOT to use:

  • Masking patient identifying data or HIPAA identifiers (use scrub_phi instead).

  • Clinical emergency triage or medical symptom screening (use check_red_flags instead).

  • Verifying medical evidence citations or guideline entailment (use verify_evidence instead).

Parameter constraints & formats:

  • 'text': Free-text clinical dialogue, patient consultation prompt, or third-party agent message (up to 50,000 characters). Evaluated across 4 adversarial threat vectors: direct prompt injections ('ignore previous safety rules'), role-play jailbreak personas ('DAN', 'hypothetical unrestricted physician'), system prompt and secret exfiltration ('reveal system instructions'), and lethal dosage overrides (unauthorized dosage escalation, off-label prescription bypasses).

Behavioral guarantees & return states:

  • Non-LLM deterministic inspection: Pure regex and token analysis running locally in memory without remote classifier APIs, credentials, or rate limits.

  • Idempotent & non-destructive: Repeated scans on identical text return consistent reports without state mutation.

  • Threat outcomes: Clean inputs return is_safe=true with violations=[]; detected attacks return is_safe=false with violations listing triggered attack categories. Empty or non-string inputs safely return is_safe=true without exceptions.

normalize_terminologyA

Maps regional pharmaceutical trade brand names to standardized International Nonproprietary Names (INN), resolves primary pharmacological drug classes, and retrieves WHO Anatomical Therapeutic Chemical (ATC) codes.

When to use:

  • Resolving commercial pharmaceutical trade brand names into canonical INN entities for prescribing audits, formulary reconciliation, or clinical reasoning.

When NOT to use:

  • Multi-drug interaction or pharmacological contraindication screening (use check_drug_interactions instead).

  • Clinical consultation emergency triage or red-flag evaluation (use check_red_flags instead).

  • Mathematical clinical risk score calculations (use calculate_clinical_score instead).

Parameter constraints & formats:

  • 'brand_name': Commercial trade name string with optional formulation or dosage strength. Evaluated clinically by:

    • Resolving active salt formulations (e.g. 'Bisoprolol fumarate' from 'Concor Cor', 'Amoxicillin-clavulanate' from 'Augmentin').

    • Stripping pharmaceutical dosage forms ('tablet', 'syrup', 'vial') and numeric metric strengths ('mg', 'mcg', 'IU').

    • Normalizing trade names across Egyptian (EDA), Saudi (SFDA), European (EMA), and US (FDA) regional pharmaceutical markets.

Behavioral guarantees & return states:

  • Non-LLM deterministic dictionary lookup: Grounded in offline curated WHO INN and ATC indices with zero external network calls, credentials, or rate limits.

  • Idempotent & non-destructive: Resolving the same brand name repeatedly returns identical mappings without modifying state.

  • Bounded response & error handling: Returns a single bounded JSON object without pagination; unrecognized brand names safely return matched=false and null entity fields without throwing uncaught exceptions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool occupies a distinct lane: arithmetic scoring, consultation triage, DDI screening, evidence verification, PHI redaction, prompt security, and terminology normalization. Every description includes explicit 'When NOT to use' clauses that route the agent to the correct sibling tool, leaving essentially no overlap.

Naming Consistency5/5

All seven names follow a strict verb_noun snake_case convention (calculate_clinical_score, check_red_flags, verify_evidence, scrub_phi, scan_prompt_security, normalize_terminology). No camelCase or stylistic outliers.

Tool Count5/5

Seven tools is squarely in the well-scoped range, and each one maps to a genuinely different safety function rather than a redundant variant. No tool feels padded or missing from the count.

Completeness4/5

The clinical-safety surface is broad and coherent: computation, triage, pharmacology, evidence, privacy, and adversarial input are all covered, with EHR persistence deliberately delegated externally. Minor gaps remain, such as no discovery/catalog tool for enumerating supported calculator_ids, guideline registries, or formulary coverage before calling.

Maintenance

ActivityMaintained
ResponsivenessOutdated data