Clinic Laboratory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLINIC_DB_PATH | No | Path to the SQLite database file. Defaults to data/clinic.db if not set. |
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 |
|---|---|
| search_patientsA | Find a patient by medical record or partial name before requesting clinical data. |
| get_latest_lab_resultsA | Get the newest result for each test of a patient, or for one test code. |
| compare_lab_resultsB | Compare the earliest and latest result of one test in an optional YYYY-MM-DD range. |
| record_lab_resultC | Record a laboratory result and optionally complete the matching pending exam. |
| list_pending_examsA | List pending exams for every patient or one medical record, optionally overdue only. |
| schedule_lab_examC | Schedule a laboratory exam using YYYY-MM-DD order and due dates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| lab_test_catalog | Return the test codes included in the demonstration dataset. |
TDQS
Scored across 6 tools
Each tool targets a distinct action in the lab workflow: scheduling, recording, searching, retrieving, comparing, and listing pending exams. There is no meaningful overlap between tool purposes, so an agent can reliably select the right tool.
All tool names follow a consistent snake_case verb_noun pattern, such as record_lab_result, schedule_lab_exam, and list_pending_exams. Modifiers like 'latest' and 'pending' are used uniformly and do not break the convention.
Six tools is a well-scoped count for a laboratory-focused server. Each tool covers a clear part of the domain without unnecessary duplication or bloat.
The core lab workflow is well covered: search patients, schedule exams, record results, list pending exams, and retrieve/compare results. Minor gaps exist, such as no explicit update/cancel flow for scheduled exams or recorded results, but agents can work around these for typical lab tasks.