No user-submitted related servers found.
Scored across 16 tools
Most tools have clearly distinct responsibilities, and aws_query versus run_dag is well separated by single-call versus dependent multi-step execution. The main ambiguity is among token_status, cache_status, and org_status, since org_status substantially combines the other two.
All names use readable snake_case, but their structure is inconsistent: list_roles and refresh_accounts are verb-first, while orgs_list, config_show, and config_validate are noun-first. Names such as current_org and perf_stats add further noun-phrase patterns, making the convention only moderately predictable.
Sixteen tools is slightly above the ideal range, and the separate status and diagnostic views add some weight. However, the server covers org and session management, account and role discovery, configuration, query execution, and performance diagnostics, so the count remains reasonable.
The primary workflow is covered end to end, from org selection and authentication through account discovery, deterministic role resolution, and arbitrary AWS operations, with run_dag supporting dependent calls. Minor administrative omissions such as explicit logout/session revocation and cache clearing remain, but they do not block normal discovery and querying.