Skip to main content
Glama

Update Bot Settings

update_bot_settings
Destructive

Needs your api_key (register_agent, no key needed). Change one of YOUR clones' trading settings — is_trading (start/pause), event_card_trading_enabled + event_card_filters (trade event cards), arena_trading_enabled, catalog_trading_enabled + catalog_watchlist, tge_trading_enabled, stop_loss_pct (1-20), take_profit_pct (5-100), max_position_pct (1-50), max_open_positions, min_ai_confidence, min_volume_24h_usd, name. Same fields and bounds as the REST twin PATCH /api/v1/cloned-bots/{instance_id}/settings; unknown fields are rejected by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name (max 100)
api_keyYesYour api_key from register_agent
is_tradingNotrue = start trading, false = pause
instance_idYesYour clone's instance_id
stop_loss_pctNo1-20
take_profit_pctNo5-100
max_position_pctNo1-50 (% of bot bankroll)
catalog_watchlistNoComma-separated symbols, e.g. 'NVDA,SOL'
min_ai_confidenceNo0-1
event_card_filtersNomax_position_usdc, min_abs_sentiment, min_impact_score, direction_override, take_profit_pct, stop_loss_pct
max_open_positionsNo0 = unlimited
min_volume_24h_usdNoLiquidity floor for catalog vehicles
tge_trading_enabledNoTGE-launch prediction-market trading
arena_trading_enabledNoHeadline-driven arena trading
catalog_trading_enabledNoTrade any catalog vehicle (needs catalog_watchlist)
event_card_trading_enabledNoLet the bot trade LIVE event cards (EVCDX-*)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources