Bookeo MCP by usefulapi

Each tool maps to a distinct resource+action (create/get/list/update/cancel per entity). The only near-overlaps — list_bookings vs list_customer_bookings, and get_availability_slots vs search_matching_slots — are explicitly delineated in the descriptions (product type and scope). An agent can reliably pick the right tool.

Every tool follows the exact same bookeo_<verb>_<noun> pattern (cancel_booking, create_customer, get_payment, list_customers, search_matching_slots, update_booking). Verbs are drawn from a small consistent set (create/get/list/update/cancel/search). No mixing of conventions.

21 tools is on the heavier side of ideal, but each earns its place across bookings, customers, payments, availability/holds, and settings. There is little redundancy, though the booking-listing and availability tools could conceivably be consolidated. Slightly over but justified by the domain breadth.

Strong lifecycle coverage: bookings support create/get/list/update/cancel plus holds, customers support create/get/list/update, payments are readable, and settings (business, products, resources, people categories, api key) are exposed. Minor gaps like no customer delete and no payment mutation exist, but these are plausibly absent by API design rather than oversights.