No user-submitted related servers found.
Scored across 9 tools
The descriptions do heavy lifting: scan_project, security_audit, improve_app and upgrade_readiness all derive from the same scan and could easily blur together, but each explicitly states when to prefer another tool ('use security_audit for deeper', 'use upgrade_readiness first'). Boundaries between upgrade_readiness, upgrade_plan and improve_app are deliberate and readable, though the scan/security/improve trio still requires careful reading.
All tools use snake_case and the names are short and readable, with a clear upgrade_* family. There is a minor deviation in verb placement: explain_error, scan_project, check_library, measure_bundle and verify_upgrade are verb_noun, while security_audit, upgrade_plan and upgrade_readiness are noun-first.
Nine tools is well within a comfortable range, and each covers a distinct stage of the diagnostic/upgrade workflow (error help, scan, deep audit, prioritization, go/no-go, plan, library lookup, bundle, verification). No filler tools are apparent.
The surface covers the lifecycle from understanding an error through scanning, deciding on an upgrade, planning and verifying it, plus library and bundle inspection. Gaps are minor: no tool addresses runtime/performance measurement or store-metadata generation, and everything is read-only by design, so fixes cannot be applied.