Related Servers

Most tools target a clearly distinct resource+action (scope include/exclude vs skip_module/unskip_module, pre_analyze vs upload), and descriptions explicitly fence off risky confusions such as 'never uploads' or 'call ONLY when the user asks'. The main overlap is statica_status, which already reports ruleset, metric, report-generator and last-analysis state that statica_ruleset_show, statica_metric_show and statica_report_generator_show expose individually; statica_bootstrap_detect vs statica_doctor vs statica_status also require reading descriptions to choose correctly.

All 24 tools share the statica_ prefix and snake_case, with coherent families (ruleset_show/set, metric_show/set, scope_show/exclude/include/skip_module, bootstrap_detect/begin/guard/verify/finish/abort). There is a minor ordering inconsistency: most follow noun_verb (ruleset_show, report_generator_set) while a few follow verb_noun (set_auto_analysis, get_guide, pre_analyze), though each pair is internally consistent.

24 tools is on the heavy side of the range, spread across eight areas (bootstrap, scope, rulesets, metrics, reports, analysis, status, guide). Each tool does map to a distinct operation and the show/set and skip/unskip pairs are justified, but the surface is large enough that an agent must plan across multiple families before acting.

Core lifecycle is well covered: detection, bootstrap with guard/verify/finish/abort, scope management, configuration, analysis, upload and reporting. Notable gaps remain around defect handling — reports can list suppressed defects (kinds 3, 12) but there is no tool to suppress or annotate an individual defect — and there is no way to unlink/disconnect an already-linked project or inspect historical revisions, both of which agents will likely need.