No user-submitted related servers found.
Scored across 54 tools
Many tools are carefully documented but there are multiple overlapping command families: lights_on/lights_off vs set_loco_lights vs set_layout_lights vs set_all_locos_lights, and stop/emergency_stop/emergency_stop_all/power_off_all/park_all_locomotives/secure_layout/end_session all respond to some form of 'stop'. The cross-references help, but the sheer number of composite and shortcut tools makes selection genuinely error-prone.
Most tools follow predictable list_/get_/set_ patterns, and bulk operations consistently use _all (set_all_turnouts, power_off_all, park_all_locomotives). Minor deviations like signal_off, lights_on/off, system_status, layout_status, night_mode, and day_mode are still readable and do not obscure intent.
54 tools is far beyond the 25+ threshold considered too many for a coherent MCP surface, and much of the count comes from composites and shortcuts duplicating component tools (lights_on/off, signal_off, prepare_locomotive, park_locomotive, night_mode/day_mode, start_session/end_session, secure_layout). This makes the server heavy on context and selection overhead when several tools could be consolidated via parameters.
The operational surface is impressively broad: discovery and control for power, locomotives, turnouts, signals, sensors, blocks, layout lights, and exhibition/executor modes are all covered. Minor gaps such as a dedicated read-only throttle state tool and route/automation control are workable omissions, not dead ends.
