No user-submitted related servers found.
Scored across 149 tools
Resource-group prefixes and path-derived names give agents a reasonable map, but several clusters are genuinely confusable: services_get_price vs services_get_prices vs services_orders_get_price, account_payment_methods_* vs billing_payment_methods_*, service_products_get_list vs service_types_get_list vs service_product_groups_get_list, and bonuses_activate vs bonuses_activate_bonus_case. Many descriptions are tautological path echoes (e.g. "Billing invoices create", "Gifts regen"), so the name is the only disambiguator.
Broadly snake_case with a group_resource_action shape, but the group prefix is inconsistently singular vs plural (services_/service_backups_/service_products_/service_types_, accounts_/account_payment_methods_) and some names bury the verb mid-string (services_networks_ipv4_get_list, support_rates_get_cloud_tips). There is also a misspelling (leakcheck_leack_check) and a catch-all 'other_' bucket, so the pattern is readable but not predictable.
149 tools is far beyond what an agent can select from reliably, and the surface mirrors an entire REST API path-by-path rather than a curated workflow set. Many near-duplicate read endpoints (prices, stats, schemas, limits) inflate the count without adding decision-relevant capability.
Coverage is broad across services, domains/DNS, billing, support, referrals, withdrawals, SSH keys, backups and networking, so core lifecycles are largely present. However, delete operations are conspicuously missing in several places (DNS records, domains, API keys, SSH keys), which will leave agents stuck after create/edit.