Alert

Overview

Alert includes 1 tool for this workflow area.

Available tools: manage_alerts.

Use the parameter tables and examples below as the canonical request contract.

manage_alerts

Manages persistent server-side alerts, evaluated every ~30 seconds while the terminal is connected (not tick-precise), dispatched by action. Available at Pro+ tier. action=create: registers an alert. Types: price (level above/below), indicator (value or cross vs threshold), position_event (sl_hit / tp_hit / position_closed, optional ticket filter), margin_level (below %). mode=once fires a single time; mode=recurring re-arms after cooldown_seconds. Fired events are queued durably — retrieve them with action=poll. Active-alert caps by tier: Pro 10, Team 50, Enterprise 200. Requires type and condition. action=list: lists all alerts for this license with status (active/fired/cancelled), condition, mode, fire count, and last_evaluated_at (stale while the terminal is disconnected — evaluation pauses). action=cancel: cancels an active alert by alert_id (from a prior action=create or action=list). Returns ALERT_NOT_FOUND if the alert does not exist, already fired, or was already cancelled. Requires alert_id. action=poll: drains undelivered fired-alert events (oldest first) and marks them delivered. Each event carries event_id, the alert's condition echo, the triggering values, and the fired timestamp. Events are retained 7 days; pass include_delivered=true to see the retained history. Call this periodically — alerts are pull-based, nothing is pushed.

Parameters

Example Request

{
  "tool": "manage_alerts",
  "arguments": {
    "action": "create"
  }
}