Charming

Almost every tool maps to a distinct resource and action—app CRUD, builds, routines, shares, templates, feedback, assets, docs—and the descriptions are detailed enough to prevent most misselection. The only real overlap is set_remixable/unset_remixable, which are explicitly deprecated aliases of set_template/unset_template with identical effects.

All tools follow the same imperative verb_noun pattern in snake_case, with consistent clusters like create/update/delete/list and set/unset pairs. Minor variations such as unshare_app and cancel_app_build are still predictable verbs, so the naming is essentially uniform.

At 33 tools, the surface is above the ideal range and carries some redundancy—deprecated remixable aliases and four separate feedback-related tools add selection overhead. However, the server's purpose is genuinely broad, covering app lifecycle, builds, sharing, templates, routines, assets, and docs, so the count is defensible for the scope.

Core workflows are well covered: app create/read/update/delete, source and build management, runtime data operations, sharing/revocation, templates, routines, feedback, assets, and documentation lookup. The main gaps are the lack of a claim_app flow for anonymous apps, no asset listing/deletion, and no team management beyond roles.