AgendaPro MCP by usefulapi

Each tool names a distinct resource plus action, and the descriptions actively disambiguate the risky pairs (list_clients vs search_clients, list_custom_attributes vs list_client_custom_attributes). The only soft overlap is cancel_booking vs update_booking, since a booking status can also be changed through the general update, but the cancel tool's irreversible PATCH semantics are spelled out.

Every tool follows the same agendapro_verb_noun snake_case pattern (get_, list_, create_, update_, cancel_, search_), with no verb or casing deviations. Resource nouns are used consistently across verbs.

24 tools is at the heavy end, but it reflects genuine breadth across nine resources (bookings, clients, locations, providers, services, products, sales, slots, custom attributes), each with get/list pairs. Nothing looks like filler, though it is close to the point where the surface becomes hard to scan.

Bookings and clients have full lifecycle coverage (create, get, list, update, cancel for bookings; create, get, list, search, update for clients), covering the core workflows. Sales, products, providers and services are read-only with no create/update, so payment recording and catalog management are gaps an agent must work around.