No user-submitted related servers found.
Scored across 30 tools
Most tools target clearly distinct resources or workflow stages, and descriptions distinguish similar pairs such as writeback_preview/writeback_apply and read_workspace_doc/get_project_bible. Some ambiguity remains between high-level execution tools like run_verb, run_recipe, and run_agent_brief, where an agent must infer the right abstraction level.
The set mostly follows a predictable snake_case verb_noun convention: get_asset, list_assets, update_project_bible, writeback_apply, etc. Minor deviations such as queue_status and the bare export keep it from being perfectly consistent, but overall it is highly readable.
At 30 tools, the surface is well beyond a focused toolset and covers many subdomains: generation, scanning, requirements, writeback, workspace docs, budgeting, recipes, and blueprints. Although the domain is broad, this many tools creates selection overhead and increases the chance of choosing the wrong workflow entry point.
Core asset-generation, project-bible, game-profile, requirement, budgeting, and writeback workflows are covered. However, lifecycle gaps are notable: blueprints have create-folder and delete but no list/get/update, recipes can be created and run but not listed or deleted, and assets have no update/delete operations.