No user-submitted related servers found.
Scored across 134 tools
Most tools are clearly separated by resource+action pairs (credential, invoice, domain, banner, etc.), so the majority of the 134 tools are distinguishable. A few pairs blur together—deploy_application vs control_deployment both start workloads, and list_models vs list_model_catalog overlap—while several override tools have empty descriptions, creating real misselection risk.
Tool names overwhelmingly follow the acedatacloud_verb_noun snake_case pattern, and CRUD clusters are predictable (list/get/create/update/delete). Minor exceptions like usage_summary lacking a verb and control_deployment using a vague verb keep it from being perfectly consistent.
At 134 tools, this is far beyond any well-scoped MCP surface and creates enormous selection and context overhead. Even for a broad platform, exposing nearly every operation as a separate tool is an extreme mismatch for agent usability.
The set is genuinely broad: full lifecycle coverage exists for credentials, orders, invoices, domains, banners, and overrides, plus read surfaces for docs, models, services, and usage. Some resources have workable gaps—announcements lack update/delete, surveys are read/submit only, and applications lack a dedicated delete tool—but agents can usually work around these.