No user-submitted related servers found.
Scored across 6 tools
Each tool has a clear role in the workflow, but swg_write and swg_write_cas are both write entry points and could be misselected by an agent. The detailed descriptions distinguish normal write from CAS merge write, while the other tools are cleanly separated.
All tools use the swg_ prefix and lowercase snake_case, so the set is immediately recognizable and predictable. However, swg_status and swg_gate are noun-style command names rather than verb_noun action names, a minor deviation from the otherwise verb-oriented pattern.
Six tools is well-scoped for a stale-write guard: read, write, CAS write, reacquire, gate, and status each serve a distinct purpose. No tool feels redundant, and the count matches the focused domain.
The core stale-write lifecycle is covered end-to-end: read, write, recover, verify before external action, and inspect status. Minor gaps remain around explicit path registration and the referenced reconcile step, which is not surfaced as a named tool, but agents can work around these with existing tools.