No user-submitted related servers found.
Scored across 27 tools
Tool purposes map cleanly to distinct Spinnaker resources and actions, and the descriptions actively disambiguate the tricky pairs (list_executions vs search_executions, get_pipeline vs get_pipeline_history, get_target_server_group vs list_server_groups, find_images vs get_image_tags). Minor residual overlap remains between the three pipeline-configuration tools (list_pipelines/get_pipeline/get_pipeline_history) and between execution inspection tools (get_execution/get_task), but the boundaries are described well enough to pick correctly.
Every tool follows a snake_case verb_noun convention (get_*, list_*, find_*, search_*, evaluate_*), with resource nouns that match across the family (application/account/cluster/server_group/pipeline/execution). No camelCase mixing or vague standalone verbs.
27 tools is on the heavy side, though the breadth of Spinnaker's domain (accounts, apps, clusters, server groups, instances, LBs, firewalls, networks, subnets, images, pipelines, executions, tasks) justifies most of them. A few list/get pairs could be folded into optional parameters, and the set is read-only, so the surface feels padded rather than scoped down to a workflow.
Read coverage across the domain is broad and consistent, but there is not a single mutation tool: no trigger_pipeline, save_pipeline, delete_pipeline, or strategy save — yet get_execution explicitly tells the agent to get execution_id from 'trigger_pipeline' and list_strategies mentions 'before saving or modifying one', creating dangling references and dead ends for the server's core deployment purpose. Cancel-task and pipeline-delete lifecycle operations are also absent.
