Trade universe and watchlist

get_trade_universeCopy Anchor Link

The connection's trade universe — the watchlist the user maintains in the dashboard (the MT5 Market Watch equivalent), in the user's order. Agents take their scan list from here instead of a hard-coded list. When restrict_to_universe is true, trading tools reject symbols outside it (SYMBOL_NOT_IN_UNIVERSE); analytics and market-data tools still accept any symbol. include_market_data adds min_notional_usdt, max_leverage_exchange, 24h quote volume, last price and funding. An input that could not be filled is null and listed in missing_inputs with the reason per input: errors[{input, code, retryable}] (code is the service error such as INVALID_SYMBOL or RATE_LIMITED, or NO_DATA when the exchange returned nothing). Read-only: the list is edited in the dashboard. Available on every tier.

Capability: read · read-only · REST: POST /v1/tools/get_trade_universe

Example request:

{}

manage_watchlistCopy Anchor Link

The connection's trade universe in tiers (mt_mcp parity): core and probation are tradable, candidate is shadow-only (orders refused; use track_hypothetical). Actions: list, add {symbol, tier (default candidate), reason, review_by?, notes?}, update {symbol, tier?|review_by?|notes?, reason}, remove {symbol, reason} (soft), history {symbol?}. Symbols like BTC, BTCUSDT or BTC/USDT are normalised to this connection's market. At most 100 symbols. Writes need a reason; dashboard edits share the same history. dry_run defaults to true: nothing is sent to the exchange until dry_run:false is passed explicitly. Requires the trade capability (Pro and above; simulated connections may trade on every tier).

Capability: trade · mutating · REST: POST /v1/tools/manage_watchlist

Example request:

{
  "action": "list",
  "dry_run": true
}