No user-submitted related servers found.
Scored across 37 tools
Pipelines, executions, and strategies are cleanly separated, and the descriptions explicitly disambiguate the tricky pairs (save_pipeline vs update_pipeline, list_executions vs search_executions). A few near-neighbors exist (get_cluster vs get_target_server_group vs list_server_groups), but each targets a distinct resource/action so confusion is minimal.
Names uniformly follow a snake_case verb_noun pattern (list_*, get_*, save_*, update_*, delete_*, plus consistent action verbs like trigger_pipeline, pause_execution, cancel_execution). No mixing of conventions or vague verbs.
At 37 tools this is heavy, well above the comfortable 3-15 range. The breadth of the Spinnaker domain (pipelines, executions, clusters, server groups, firewalls, networks, images, accounts) justifies many of them, but the surface is large enough to feel sprawling rather than tightly scoped.
Core lifecycle coverage is strong: full CRUD for pipelines, and comprehensive execution control (trigger, cancel, pause, resume, restart, search). Minor gaps remain in secondary resources (strategies lack get/update; applications, networks, load balancers are read-only), but these are workable.
