CareCompanion
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_PROFILE | No | A local AWS profile with bedrock:InvokeModel permissions. Alternative to providing AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. | |
| BEDROCK_REGION | No | The AWS region for Bedrock. The README pins this to us-east-1. | us-east-1 |
| AWS_ACCESS_KEY_ID | No | The AWS access key for runtime credentials with bedrock:InvokeModel. Required if not using a local AWS profile. | |
| AWS_SECRET_ACCESS_KEY | No | The AWS secret access key for runtime credentials with bedrock:InvokeModel. Required if not using a local AWS profile. |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_todays_planA | The elder's medication schedule for today — what's taken, what's next, any missed dose, upcoming appointments, and whether they've checked in. Call this first for any "what's my day" or "what do I take" question. |
| log_doseA | Record that the elder took a medication (name as spoken — brand names and "my blood pressure pill" work). A safety guard may REFUSE a duplicate or too-soon dose: when |
| skip_doseA | Record that the elder is deliberately skipping the next due dose of a medication, with an optional reason. Skipping a critical medication alerts the caregiver. |
| daily_checkinA | Record how the elder feels today: their mood plus any symptoms in their own words. Runs symptom escalation and alerts caregivers automatically for urgent or emergency symptoms. If the result contains |
| call_for_helpA | The elder asked for help or said something alarming outside a check-in ("help", "I fell", "I can't breathe"). Immediately alerts ALL caregivers and returns emergency guidance to speak verbatim. |
| add_medicationA | Caregiver adds a medication to the elder's schedule. The medication is always added; the result also carries informational interaction and allergy warnings against the elder's current medications — read every warning and the disclaimer to the caregiver. Not medical advice. |
| resolve_alertA | Caregiver acknowledges (seen, working on it) or resolves (done) an alert, with an optional resolution note for the audit trail. Safe to repeat. |
| caregiver_summaryA | Caregiver-facing summary of the elder's week: medication adherence (7 or 30 days), today's doses, open alerts, the check-in trend and upcoming appointments. Hosts that support MCP Apps also render the live family dashboard. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| morning_briefing | Speak a warm three-sentence morning briefing of the elder's day and ask one gentle check-in question. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| CareCompanion dashboard | Family caregiver dashboard (MCP App view for caregiver_summary). |
| Margaret Hart — adherence report | 7- and 30-day medication adherence for an elder (due / taken / late / missed / skipped, per day and per medication) as JSON. |
TDQS
Scored across 8 tools
Each tool maps to a distinct action (view plan, log/skip dose, check-in, call help, add med, resolve alert, summary), but get_todays_plan and caregiver_summary both surface daily doses and schedule, requiring the elder/caregiver framing to disambiguate.
Mostly imperative snake_case verbs (log_dose, skip_dose, add_medication, resolve_alert), but get_todays_plan, daily_checkin, and caregiver_summary break the verb_noun pattern slightly.
Eight tools cover the core elder-care workflows without bloat; each tool addresses a distinct need and no tool feels redundant.
Medication lifecycle is covered for daily use (plan, log, skip, add) and alert/check-in flows are complete, but there is no update/remove medication or appointment management, so minor gaps exist.