No user-submitted related servers found.
Scored across 19 tools
Most tools have clearly distinct purposes (create_job vs create_event vs create_customer are explicitly differentiated, and add_line_items vs create_job+lineItems is clarified). Minor overlap exists between get_jobs and get_schedule and between get_business_context and get_reference_data, which both return catalog/lookup data, but the descriptions give workable guidance.
Every tool follows a strict snake_case verb_noun convention (get_jobs, create_job, reschedule_job, close_jobs, cancel_job, add_line_items, set_customer_source). No camelCase or naming outliers, making the set highly predictable.
19 tools is on the heavier side but reasonable for a multi-entity domain (jobs, customers, estimates, invoices, payments, catalog, scheduling). Each tool maps to a distinct operation, though a few could plausibly be consolidated (e.g. get_reference_data vs get_business_context).
Job lifecycle is well covered (create, read, reschedule, close, cancel) and estimates/catalog have creation paths, but notable gaps exist: no update_customer, no update/delete for estimates, invoices, or line items, and no way to record payments or convert estimates to jobs. Read-only surfaces for invoices/payments leave dead ends.