FHIR-first, read-only MCP server for Practice Fusion
practice-fusion-mcp demonstrates solid definition quality across a cohesive set of FHIR-compliant healthcare read tools. All 19 tools follow consistent naming patterns (verb-first: get_*), have detailed descriptions (150-250 chars typical), and properly typed input schemas with parameter descriptions. Tool names clearly distinguish similar operations (e.g., get_patient vs get_patients vs get_everything). Descriptions are well-crafted with clear FHIR context (e.g., 'FHIR date filter, e.g. ge2026-07-01'). All parameters are typed and described. However, output schemas are not explicitly documented in the visible code, tool definitions show input schemas clearly but return types are referenced via 'shaped' functions (shapeAppointment, etc.) which are not fully visible in the provided source. This indirect schema documentation prevents a higher score. Additionally, error handling is minimal, no evidence of actionable error messages, recovery guidance, or categorization. All tools are read-only (no destructive operations), which eliminates security risks but also means no confirmation patterns or permission gates are needed. Composition is strong: each tool does one thing, naming is unambiguous, and parameter naming (patientId, status, limit) matches typical FHIR conventions.
List allergies and intolerances for a patient. Returns shaped allergy summaries. Read-only.
List Practice Fusion appointments, optionally filtered by patient, status, and date. Dates use FHIR prefixes, e.g. ge2026-07-01 (on/after) or le2026-07-31 (on/before). Returns shaped appointment summaries. Read-only.
List care plans for a patient. Returns shaped care plan summaries. Read-only.
List active conditions for a patient. Returns shaped condition summaries. Read-only.
List insurance coverage for a patient. Returns shaped coverage summaries. Read-only.
List diagnostic reports for a patient. Returns shaped diagnostic report summaries. Read-only.
Output schemas not explicitly documented in code. Tool definitions reference 'shaped' functions (shapeAppointment, etc.) but the return type structure is not visible in the provided source. LLMs cannot infer what fields to expect without documented output schemas.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 35 | 2025-06-18+ | v2 |
List clinical documents for a patient. Returns shaped document reference summaries. Read-only.
List clinical encounters for a patient. Returns shaped encounter summaries. Read-only.
Get all resources linked to a patient (FHIR $everything operation). Returns all clinical and administrative data for a patient. Read-only.
List health goals for a patient. Returns shaped goal summaries. Read-only.
List immunization records for a patient. Returns shaped immunization summaries. Read-only.
List laboratory observations for a patient. Returns shaped lab result summaries. Read-only.
List active medications for a patient. Returns shaped medication summaries. Read-only.
Search for organizations by name or identifier. Returns shaped organization summaries. Read-only.
Get a single patient by FHIR resource id. Returns shaped patient summary. Read-only.
Search for patients by name, identifier, birthdate, or gender. Returns shaped patient summaries. Read-only.
Search for practitioners by name or identifier. Returns shaped practitioner summaries. Read-only.
List procedures for a patient. Returns shaped procedure summaries. Read-only.
List vital sign observations for a patient. Returns shaped vital summaries. Read-only.
Error handling is not documented or visible. No recovery guidance, error categorization, or actionable error messages evident in code. LLMs need to know whether errors are retryable, user-fixable, or fatal.
Pagination behavior not explicitly documented. Tools like get_appointments and get_patients accept 'limit' parameter, but descriptions do not state default values, maximum allowed, or whether results are truncated when limit is exceeded. No mention of offsets, cursors, or total counts.
Parameter 'limit' lacks explicit constraints in descriptions. No mention of minimum (1?), maximum (100?), or default value (50 is mentioned in get_appointments only). LLMs may pass invalid limits without clear guidance.
FHIR date filter format is documented with examples (e.g. ge2026-07-01) but no formal constraint or validation guidance provided. LLMs may misinterpret prefix syntax or omit dates entirely.