No user-submitted related servers found.
Scored across 20 tools
Most tools are clearly distinct by resource type (e.g., search_encounter vs. search_condition). The generic fhir_get/fhir_search overlap with specific wrappers, but descriptions clarify their broad vs. focused nature. A few potential confusions exist (e.g., list_allergies vs. search_condition), but overall boundaries are clear.
Tool names are all snake_case but mix verb styles: get_ (get_patient), search_ (search_encounter), list_ (list_allergies), fhir_ (fhir_get), plus standalone names (whoami, connect_practice). This inconsistent verb choice across similar operations (e.g., search_observation vs. list_immunizations) makes the pattern less predictable.
20 tools is reasonable for a FHIR server covering authentication, generic FHIR operations, and a broad set of clinical resource types. While slightly on the higher side, each tool serves a distinct resource or workflow, and the count matches the domain complexity.
The toolset covers core FHIR resources (Patient, Encounter, Observation, Condition, MedicationRequest, etc.) with both list and search capabilities. Missing common resources like DiagnosticReport or Procedure can be accessed via generic fhir_search, so agents can work around gaps. The read-only scope is consistent with the OAuth launch context.
