No user-submitted related servers found.
Scored across 34 tools
Most tools target a distinct resource+action and the descriptions actively route the agent (apply_blueprint_graph is the 'main path', connect_pins/delete_node are 'surgical fixes'; compile_and_diagnose is the fallback for compile_blueprint). A few boundaries still need the prose to separate: compile_blueprint vs compile_and_diagnose, check_health vs run_diagnostics, verify_behavior vs verify_scenario, and build_blueprint vs build_batch vs apply_blueprint_graph. The 'prefer X unless Y' guidance makes these resolvable, so overlap is minor rather than confusing.
Nearly all tools use the ue5_ verb_noun snake_case pattern (start_pie, read_pie_state, connect_pins, delete_asset, verify_behavior). Minor deviations: noun-first task_list and tool_search break the verb_noun ordering of task_begin/task_step/task_end, and screenshot is a bare noun. The convention is still readable and predictable overall.
34 tools is above the comfortable band and the surface is heavy for an agent to hold in context, with the 101-command escape hatch meaning some dedicated tools are conveniences. However, the domain genuinely spans Blueprint authoring, PIE runtime verification, asset management, acceptance scenarios, tasks, and diagnostics, and each tool maps to a real capability rather than a duplicate. Borderline-heavy but not bloated.
Blueprint coverage is near-complete (search/read/create/apply/wire/disconnect/delete/compile/diagnose), plus full PIE lifecycle and runtime assertion, screenshots, logs, asset list/save/delete, and an execute_command/tool_search escape hatch for materials and UMG. Gaps are minor: no asset rename/duplicate, no pause/resume PIE, and non-Blueprint asset creation only via the generic command path.