No user-submitted related servers found.
Scored across 14 tools
Most tools target clearly distinct operations (load scenario, set faults, advance clock, rewind), and descriptions actively disambiguate close pairs, e.g. twin_export_log points to twin_changes for a summary and twin_reset points to twin_rewind for partial undo. The main residual confusion is the read/write pair twin_webhooks vs twin_set_webhooks, and the three 'restore world' tools (reset, rewind, load_scenario), which descriptions clarify but which still sit close together.
Every tool uses the same 'twin_' prefix and snake_case, giving a strong shared identity. The verb position is mostly predictable (twin_set_*, twin_list_*, twin_export_*, twin_advance_*), but read-only getters break the pattern by using bare nouns (twin_status, twin_webhooks, twin_changes, twin_checkpoint), creating an asymmetry with twin_set_webhooks.
Fourteen tools is well within the sweet spot and each maps to a distinct responsibility in the simulation lifecycle: world setup, environment knobs, time control, observation, and rollback. Nothing feels padded or bolted on.
Lifecycle coverage is strong: build/load a world, configure faults, auth and webhooks, move time, trigger actions, observe via status/log/changes, and roll back via checkpoint/rewind/reset. The notable gap is there is no way to inspect the twin's actual records (customers, invoices, jobs) directly—only event streams and status—and no way to delete or list a single checkpoint.