No user-submitted related servers found.
Scored across 34 tools
Most tools target a distinct Tebra resource and action, and descriptions clearly separate similar entities like appointments vs. appointment details and patients vs. patient searches. A few adjacent pairs such as get_charges/get_payments/get_transactions or check_insurance_eligibility/get_patient_authorizations could be confused, but the descriptions draw reasonable boundaries.
Every tool follows the tebra_ prefix with a consistent verb_noun snake_case pattern, such as get_patient, create_appointment, update_encounter_status, and delete_document. There are no mixed conventions, vague verbs, or unpredictable naming styles.
With 34 tools, the server is well beyond the typical well-scoped range and adds significant selection overhead for an agent. While most tools serve distinct purposes, the overall surface feels heavy for a single MCP server.
Core patient, appointment, encounter, and payment workflows are substantially covered, including create/read/update/status operations. However, there are notable gaps such as no encounter detail editing, no document retrieval/listing, and no creation or update of authorizations or patient cases.