No user-submitted related servers found.
Scored across 17 tools
Each tool targets a distinct resource or action: booking lifecycle actions (cancel, reschedule, assign), customer/provider CRUD-style reads, invoice/draft sends, and dashboard reporting are clearly separated. The two sending tools target different objects (invoice vs. quote draft), so they should not be confused.
Nearly all tools follow a snake_case verb_noun pattern (list_bookings, get_customer, create_booking, resend_invoice). The only deviation is dashboard, which is noun-only, so the convention is predictable but not perfectly uniform.
Seventeen tools is slightly above the typical 3-15 range but reasonable for a booking-admin domain spanning bookings, customers, providers, invoices, charges, drafts, and reporting. Each tool maps to a recognizable resource or action rather than feeling padded.
Read coverage is broad, but lifecycle coverage is uneven: there are no update operations for customers, bookings, or providers, no create-booking-from-scratch path, and no invoice or charge creation. Most critically, list_charges explicitly points to refund_charge, which is not present, creating a dead end for refund workflows.