No user-submitted related servers found.
Scored across 15 tools
Most tools have clearly distinct purposes, and the auth lifecycle (session_status, request_sign_in_link, verify_sign_in_token, verify_sign_in_pin, sign_out) is well separated with token-vs-PIN clearly differentiated. Minor overlap exists between list_document_requests vs list_documents and list_billing_items vs get_billing_overview, but the descriptions do enough to tell them apart.
All tools share the simplepractice_ prefix and use consistent snake_case with a verb_noun pattern (get_, list_, verify_, request_, sign_out). The main deviations are noun-only names like session_status and healthcheck, which break the verb-first pattern but remain readable and unambiguous.
Fifteen tools sit at the top of the ideal range but each earns its place: five auth tools, four read collections, two billing views, two document views, plus account and healthcheck. Slightly heavy, but no obvious filler.
The read-only Client Portal surface is well covered: account, auth, appointments, billing, documents, announcements, and document requests, plus a diagnostic healthcheck. Gaps are the write/action operations a portal client could still want — submitting document-request answers, marking announcements read, or requesting/canceling appointments — which agents cannot work around but are plausibly out of scope.