MedMemory
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_medicationsA | Returns all currently active medications for the patient. Use this when the user asks what medications they are taking, what drugs they are currently on, or what their current prescriptions are. Filters out completed medication courses automatically. |
| get_lab_trendB | Returns a list of all readings for that marker, oldest first. Use this when the user asks about trends, progress, changes over time, historical readings or whether something is getting better or worse for a specific lab marker. |
| ingest_health_documentsA | Ingest a health document (PDF or image) into the MedMemory database. Use this when the user wants to add a prescription, lab report, or any medical document to their health record. Extracts medications, lab results, diagnoses, and allergies automatically using AI. Args: file_path: Absolute path to the PDF or image file to ingest. |
| get_allergiesA | Returns all recorded allergies for the patient. Call this when the user asks about:
|
| get_visit_historyB | Use this tool when asked about:
|
| get_vaccination_statusA | Returns all recorded vaccinations and flags overdue or missing ones. Use this when the user asks about:
|
| check_drug_interactionA | Check if a newly prescribed drug interacts with current medications. Use this when the user:
Args: new_drug: Name of the newly prescribed drug to check (generic or brand name) |
| generate_health_summaryA | Generate a complete health summary suitable for sharing with a new doctor. Use this when the user asks for :
No inputs needed - pulls all data from the health record automatically. |
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
Each tool has a clearly distinct purpose: drug interaction checking, health summary generation, allergies, medications, lab trends, vaccinations, visit history, and document ingestion. No two tools overlap in functionality, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_allergies, generate_health_summary, ingest_health_documents). The verbs are appropriately descriptive and uniform, with no mixing of styles.
With 8 tools, the server is well-scoped for a personal health record assistant. Each tool provides a distinct value, and the count is neither too thin nor overwhelming for the domain.
The tool set covers core health record operations: retrieving medications, allergies, vaccinations, lab trends, and visit history, plus drug interaction checks and document ingestion. Missing are update or delete capabilities, but these are likely out of scope for a retrieval-focused assistant.