No user-submitted related servers found.
Scored across 27 tools
Several tools overlap in purpose: list_apis, get_api_spec, get_apis_id, get_services_apis and get_service/get_pricing all revolve around API/service metadata, and list_docs vs search_docs vs get_document vs get_documents_openapi.json require careful reading to separate. Descriptions do cross-reference each other (list_docs vs search_docs) which helps, but the auto-generated 'Get X id' tools (get_apis_id, get_datasets_id, get_integrations_id, get_coin_policies_id) are indistinguishable from their list/get counterparts.
Most tools follow acedatacloud_verb_noun in snake_case, but the pattern breaks with path-derived names like get_apis_id, get_services_apis, get_documents_openapi.json (literal .json suffix), list_site_home_sections_public, and get_recharge_cards_allocations_token. The prefix is consistent, but the verb/resource ordering is not.
27 tools is on the heavy side for what appears to be a platform metadata/read surface, and a number of them (the generic '_id' getters) feel auto-generated rather than purposefully scoped. The domain is broad, so it is borderline rather than clearly excessive.
The surface is almost entirely read-oriented (list/get) with no create/update/delete tools despite the usage guide referencing a 'write-confirmation model', leaving a notable lifecycle gap. Read coverage across services, docs, datasets, integrations and models is fairly broad but inconsistent.