Schema | Clinic Laboratory MCP Server

Clinic Laboratory MCP Server

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.

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.

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`	{}

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`lab_test_catalog`	Return the test codes included in the demonstration dataset.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MiltonPolanco/clinic-lab-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server