dingdawg-healthcare-agent
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| patient_intakeA | Free AI patient intake form with triage priority and symptom analysis. Returns structured intake locally. Deep LLM-powered ICD-10 coding and clinical reasoning with API key. |
| clinical_summaryA | Summarize clinical notes into structured format. Extracts chief complaint, HPI, assessment, plan. Requires DINGDAWG_API_KEY for LLM-powered summarization. |
| hipaa_checkA | Free HIPAA compliance quick check for processes and systems. Returns basic compliance gaps locally. Deep LLM-powered audit with API key. |
| appointment_schedulerC | AI-powered appointment scheduling with conflict detection and optimization. Requires DINGDAWG_API_KEY. |
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 4 tools
Each tool targets a distinct healthcare function—patient intake, clinical summarization, HIPAA compliance, and scheduling. There is no overlap in purpose or output, making misselection unlikely.
All tool names follow a consistent <domain>_<function> snake_case pattern (e.g., patient_intake, hipaa_check). The suffix types vary between nouns and verbs, but the overall naming is predictable and uniform.
Four tools is a reasonable, focused set for a healthcare agent, each earning its place in the workflow. The count is slightly lean but still well-scoped.
The set covers intake, summarization, compliance, and scheduling, but lacks basic CRUD operations for patients or appointments (e.g., no get, update, or delete). This leaves notable gaps for ongoing management.