Skip to main content
Glama
Sign In
clinic-mcp-server

clinic-mcp-server

by leomengineer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get patient record

get_patient_record
Read-only

Retrieve patient details including name, insurance, last visit, and next appointment by patient ID. Returns an error if patient not found or database unavailable.

Instructions

Look up a patient by id: name, insurance, last visit, and next confirmed appointment.

Raises a tool error if the patient does not exist or the database is down —
never returns an empty success that could be mistaken for 'no appointments'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "patient_id": "<patient_id>"
    },
    "name": "get_patient_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
patient_idYesStable patient id. Demo patient: 'jordan-lee'.

Output Schema

NameRequiredDescriptionDefault
statusNook
patientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds error behavior (raises error if patient doesn't exist or DB down, never returns empty success) beyond annotations (readOnlyHint, destructiveHint). Provides useful safety context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, no fluff. Efficiently communicates what it does and key behavioral note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with annotations and output schema, the description adds specific fields returned and error handling. Adequate for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear description including a demo value. Description adds no further parameter detail beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Look up a patient by id' and lists specific fields returned. Distinct from siblings: search_clinic_docs, list_appointments, create_appointment are different resources/actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for retrieving patient info by ID, but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives despite sibling list being available.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools