No user-submitted related servers found.
Scored across 28 tools
The surface is large but the descriptions carefully draw boundaries: notes vs logs vs extra properties vs tags, acknowledge vs close vs snooze vs escalate, and get_on_call vs get_next_on_call vs get_schedule_timeline are all explicitly contrasted. A few pairs (jsm_add_alert_note vs jsm_add_alert_extra_properties, jsm_add_alert_tags vs jsm_add_alert_extra_properties) could still be momentarily confused, but the docs resolve it.
Every tool uses the consistent jsm_ prefix followed by verb_noun in snake_case (jsm_list_alerts, jsm_update_alert_note, jsm_get_on_call). The pattern is uniform across alerts, notes, tags, properties, and scheduling families with no deviations in casing or style.
28 tools is heavy for a single server, sitting above the comfortable 3-15 band. The breadth reflects a genuinely large API (alerts plus on-call scheduling plus a capability-introspection tool), so each tool has a real purpose, but the count is borderline and increases selection burden.
Coverage is strong: full alert lifecycle (create/get/list/update/ack/close/snooze/escalate/delete), note CRUD, tags and extra-properties add/remove, responder addition, async verification, and schedule/on-call reads. The main gap is the inability to remove a responder, and there is no listing of teams/escalation policies/users that some write tools (escalation_id, responder_id) would benefit from.