No user-submitted related servers found.
Scored across 17 tools
Most tools have distinct roles, but several movement tools overlap in surface: aim, nudge, sweep, go_to, zoom, and run_shot all move axes, and an agent must read descriptions closely to pick the right one. The descriptions do differentiate them effectively (absolute vs relative vs smooth-timed vs labeled-direction vs multi-step), and pairs like plan_shot/run_shot and mark_view/check_view are clearly complementary.
Names are consistently snake_case, with single verbs (aim, nudge, sweep, zoom, look) for atomic actions and verb_noun compounds (run_shot, track_start, mark_view, check_view, aim_learn) for compound operations. Minor deviations like camera_status (noun_noun) and go_to (verb_prep) break the verb pattern slightly but remain readable and predictable.
17 tools is slightly heavy but each earns a place: movement (aim, nudge, sweep, zoom, recentre, run_shot, plan_shot, go_to), tracking (track_start/status/stop), observation (look, mark_view, check_view), and calibration/presets (camera_status, aim_learn, aim_list). The one genuine redundancy is the plan/execute split, which still adds validation value.
The surface covers the full PTZ lifecycle: status/ranges, single- and multi-axis movement, smooth sweeps, tracking with evidence, named presets, image capture and comparison. The main gap is no explicit abort/cancel for an in-flight run_shot or sweep (only track_stop exists for the follow loop), which agents must work around with timeouts.