No user-submitted related servers found.
Scored across 6 tools
The six tools span reasonably distinct domains (workflow, project, symbol, change review, cache, workspace), and the descriptions explicitly instruct the agent on routing order (workflow first, project vs workspace by root type). However, there is real overlap: workflow's diagnose_issue and before_edit duplicate project's diagnose mode and change_review's impact mode, and three tools share engine-backed job modes, so misselection is likely without careful reading of each description.
All names follow a strict pattern: codelattice_ prefix plus a snake_case domain noun (workflow, project, symbol, change_review, cache, workspace). It is noun/domain-based rather than verb_noun, but it is applied uniformly with no style mixing, making the set predictable.
Six tools is a well-scoped surface for a static-analysis server, and each maps to a recognizable concern (routing, project, symbol, review, workspace, cache). The caveat is heavy mode multiplexing — a single tool like codelattice_symbol hides search/context/callers/callees/job/job_status/job_detail — which makes the effective surface larger than six suggests.
The lifecycle is well covered for the stated domain: orientation, structural analysis, symbol/call-graph queries, pre- and post-edit impact and breaking-change review, plus cache management. Minor gaps exist — no explicit file content read or per-file inspection tool, and no dependency/license/vulnerability analysis — but agents can largely work around these via symbol and project queries.