No user-submitted related servers found.
Scored across 4 tools
Each tool has a clearly distinct purpose: chat handles model conversations, decide handles typed decision questions, and cancel_job/check_status manage async job lifecycle from opposite angles. Boundaries are reinforced by explicit modes and output types, so misselection is unlikely.
All names use lowercase snake_case and readable verbs, but the pattern is not fully uniform: cancel_job and check_status follow verb_noun, while chat and decide are bare verbs. This is a minor deviation rather than a confusing mix.
Four tools is well-scoped for a unified chat/decision server: chat, one async job control pair, and decide. Each tool has a clear role, and the surface does not feel thin or bloated.
Core capabilities are covered: multi-mode model chat, decision queries, and async job cancellation/status. A minor possible gap is explicit retrieval of completed async job results, though this may be handled through chat continuation_id.