Scored across 26 tools
Tools cluster into clear phases (local dev, account, listing, publishing, analytics) and descriptions explicitly cross-reference the right sibling, e.g. preview vs playtest vs run_autotest. A few pairs still brush against each other — analyze_project vs check_integration (both static inspection), get_status vs list_versions (both report version state) — but the descriptions disambiguate with 'use X for Y, Z for W' guidance.
Every tool is snake_case with a uniform gamealia_ prefix and most follow verb_noun (create_game, upload_version, list_versions, get_stats). Minor deviations exist: bare-domain names like gamealia_accounts, gamealia_whoami, gamealia_build, plus a playtest_/playtest_act/playtest_stop sub-family that breaks strict verb_noun but is internally readable.
26 tools is slightly heavy, but the surface maps a genuinely multi-stage pipeline (analyze → integrate → check → autotest → playtest → listing → upload → submit → stats), so nearly every tool has a distinct job. Only playtest/playtest_act/playtest_stop and the autotest trio inflate the count for a single function.
Happy-path lifecycle is well covered from SDK integration through review and earnings, but lifecycle dead ends remain: no delete/archive/unpublish for games or versions, no accept/decline for the pending invites that gamealia_accounts surfaces, and no way to see a single game's full listing text/edit stats beyond what get_status texts:true gives. Agents can mostly work around these, but they are real gaps for a publishing platform.
