DrChrono MCP by usefulapi

Each tool targets a distinct resource: create_appointment, create_patient, get_patient, and the list_* tools are each scoped to a clearly different DrChrono entity (appointments, patients, doctors, offices, allergies, medications, problems, clinical notes, lab orders, lab results, line items, patient payments). There is no functional overlap or boundary confusion between any two tools.

All 15 tools follow a strict namespace + verb_noun pattern (drchrono_create_*, drchrono_get_*, drchrono_list_*). The convention is applied uniformly with no camelCase or style mixing, making the set highly predictable.

15 tools is well within a healthy range and each earns its place by covering a distinct DrChrono resource. The set maps cleanly onto the practice's major data domains without redundant or filler tools.

The surface is read-heavy (12 of 15 tools are list_*) with only two create operations and a single get. There is no update, delete, or cancel for any resource, so common workflows like modifying a patient or rescheduling/cancelling an appointment hit a dead end despite create+list being present.