Scored across 74 tools
Most tools target a clearly distinct Infomaniak resource and action, and the consistent prefix makes them easy to scan. A few close pairs exist — get_my_profile vs get_my_security, get_domain vs get_domain_full, get_mailbox_info vs get_mailbox_full — so agents may need to read descriptions carefully before selecting.
A majority of tools follow infomaniak_<verb>_<noun>, and all names are readable snake_case. However, DNS tools invert this pattern (dns_create_record vs create_mailbox), Node.js tools use mixed noun-first forms (nodejs_app_status vs get_nodejs_app), and a few names like overview, help, short_urls_quota, and api_call do not follow the verb_noun convention.
74 tools is far beyond the moderate range and exceeds even the 50+ extreme threshold. The broad Infomaniak product suite partly explains the count, but this should be split into product-scoped servers or significantly consolidated, because the current surface imposes a very large selection burden on an agent.
There is good lifecycle coverage for DNS, certificates, databases, mailboxes, and several create/list/delete workflows, and infomaniak_api_call provides an escape hatch for missing public API operations. Still, obvious gaps exist: no update/reset for mailbox or hosting users, no delete for short URLs, no alias deletion for mailboxes, and kDrive/VPS areas are entirely read-only. These gaps will require workarounds for common management tasks.