No user-submitted related servers found.
Scored across 14 tools
Most tools map to a distinct action: room lifecycle (create/connect/status/disconnect/end_room/handoff), editing (read_file/apply_changes/select), and a clearly namespaced runtime_* family. The only real overlap is between crabrix_snapshot, crabrix_read_file and crabrix_status, which all read project state and require the reader to parse the descriptions to choose correctly.
All names use snake_case with a uniform crabrix_ prefix, and the runtime sub-system is consistently grouped as crabrix_runtime_*. The only deviation is that some names are verb-only (crabrix_select, crabrix_create, crabrix_connect) while others are verb_noun (crabrix_read_file, crabrix_apply_changes), but the style remains predictable and readable.
Fourteen tools sit comfortably in the sensible range for a domain covering rooms, encrypted sharing, file editing and sandboxed execution. The runtime surface consumes four tools (clients/request/start/job), which is slightly granular but each has a distinct role in the permission-to-execution flow.
The room lifecycle is well covered end to end: create, join, inspect, read/write content, share, disconnect and close, plus a full request-allow-start-poll-stop execution path. Minor gaps exist around file operations (no explicit create/rename/move beyond apply_changes with new or null text) and no notion of listing or waiting on rooms, but core workflows have no dead ends.