No user-submitted related servers found.
Scored across 40 tools
Most tools have clearly distinct purposes, and the descriptions go out of their way to explain boundaries (e.g. scan_fx vs. instrument_inventory, capture_track_audio vs. analyze_track). However, several insertion tools overlap conceptually (insert_midi_file, insert_midi_events, insert_groove, insert_riff, cut_band, insert_performance_audition), and the measurement/capture family is dense, so an agent could still hesitate in a few cases.
All names are snake_case, which is consistent, but the verb pattern is mixed: many tools use verb_noun (get_status, insert_midi_file, set_fx_param), while several core tools are bare nouns (transport, track, fx, markers, batch, instrument_inventory). It remains readable, but it is not a predictable verb_noun convention throughout.
At 40 tools, this is well above the typical 3–15 range and hits the rubric's '25+' threshold for too many. The REAPER domain is broad enough to justify a large surface, but the set still feels heavy and likely imposes a high selection burden on an agent.
The surface covers a wide lifecycle: project context, tracks, FX chains and parameters, automation, MIDI insertion, rendering, audio analysis, presets, MIDI inputs, and saving. Minor gaps remain—no open/create/close project tools, no routing write tools, limited media-item manipulation beyond deletion, and saved FX-chain management is referenced but not exposed—though raw_command provides an escape hatch.