No user-submitted related servers found.
Scored across 42 tools
Most tools target a distinct resource+action and are easy to tell apart (preset CRUD, per-subsystem settings setters, looper, MIDI, samples). A few clusters risk misselection: change_effect vs add_effect/edit_effect, save_preset vs create_preset vs copy_preset, and backup_preset vs export_sample/export_loop all share similar semantics, though the descriptions do disambiguate them.
The dominant pattern is verb_noun (get_status, list_presets, save_preset, add_effect, import_sample), which is readable and predictable. But conventions are mixed: parameter edits use both edit_effect and set_mixer/set_global/set_tuner, file export uses both backup_preset and export_loop/export_sample, and several tools are noun-only or odd (midi_assignments, looper_control, factory_reset, end_audition).
42 tools is heavy for a single hardware pedal and pushes past the comfortable 3-15 band. The breadth is real (presets, effects, mixer, vocal FX, global, tuner, drums, display, system bytes, looper, MIDI, samples, Bluetooth), but the fine-grained per-subsystem setters (set_mixer, set_vocal_fx, set_global, set_tuner, set_drum, set_display) could plausibly be collapsed into fewer dispatchers.
Coverage is unusually thorough: full preset lifecycle including backup/restore/audition, effect chain manipulation, every settings subsystem, looper, MIDI assignments, sample slots and raw system state. The main gap is that there is no way to delete/clear a preset slot (only overwrite it), and per-effect inspection relies on get_preset rather than a targeted getter.