No user-submitted related servers found.
Scored across 28 tools
Several tools overlap heavily around APIs, docs, services, datasets, and integrations: for example, list_apis vs get_services_apis vs get_apis_id vs get_api_spec, or list_docs vs search_docs vs get_doc vs get_documents_openapi.json. Multiple autogenerated-looking get_*_id tools have vague descriptions that do not clearly distinguish them from their list_* counterparts. This creates real misselection risk.
All tools use the acedatacloud_ prefix and snake_case, which is consistent, but the noun patterns are uneven and sometimes awkward. Names like get_apis_id, get_services_apis, list_site_home_sections_public, and get_documents_openapi.json break from a clean verb_noun convention. The set remains readable but not fully predictable.
With 28 tools, the set is heavy for the apparent scope and includes several autogenerated or low-value endpoints that feel redundant. The count exceeds the typical well-scoped range and likely burdens tool selection. A leaner surface focused on core platform resources would be more appropriate.
The server covers many read-oriented platform areas: services, APIs, pricing, docs, blog posts, datasets, integrations, models, announcements, and showcases. However, it lacks clear write/update/delete lifecycle coverage despite references to a write-confirmation model, and some resources only have odd partial access points. Notable gaps remain for an agent trying to manage the platform end-to-end.