No user-submitted related servers found.
Scored across 167 tools
With 167 tools, significant overlap exists between generic utilities (add_node) and specific variants (add_mesh_instance, add_audio_player). Multiple property accessors (get_node_properties, batch_get_properties, get_game_node_properties) operate in different contexts but have minimal descriptions that fail to clarify when to use each, causing high risk of misselection.
While predominantly using snake_case verb_noun patterns, inconsistencies emerge with tilemap_* prefixing, godot_* prefixing for connection tools, and mixed verb choices (add/create/remove/delete). Some tools use noun_verb ordering (uid_to_project_path) while others use verb_noun, and similar operations lack parallel structure (cross_scene_set_property vs batch_set_property).
At 167 tools, this vastly exceeds the 50+ threshold for extreme mismatch. Despite Godot's complexity, this quantity will overwhelm agent context windows and selection logic. A more coherent design would use fewer tools with parameters rather than discrete endpoints for every operation.
The set provides extensive coverage across Godot subsystems including scene management, scripting, animation, audio, physics, UI, and testing. While the granularity is inconsistent (some operations have specific tools while others rely on generic ones), there appear to be few functional gaps for core game engine workflows.