The full list of the 70+ MCP tools your AI assistant can call, grouped by category, plus the signal-condition JSON shape.
The MCP server exposes 70+ tools organized by category. Your AI assistant can
call any of these tools. Use this page when you want to know whether a
particular platform operation is reachable from your client.
add_signal_rule, edit_signal_rule and add_bias_rule take a conditions
array — the JSON form of what the builder's Condition rows express (see
signals for the UI version). Each leaf compares one
line against a constant or another line:
The line being tested, e.g. RSI.rsi, or a price line (close)
trigger
Operator: crossover, crossunder, gt, ge, lt, le, eq
threshold_value
Compare against a constant — or —
threshold_line
compare against another line, e.g. MACD.signal
trigger_line_shift / threshold_line_shift
Optional look-back in candles (default 0)
crossover / crossunder are the event operators (fire once on the cross);
gt / lt and friends are state operators (true while the condition holds).
A bias rule uses the same shape but takes a bias_direction
(long / short / neutral) instead of trigger_action.
The grid tools model the full research loop: create a template, check the
variation count, launch it, wait for it to finish, analyze the robustness
verdict, then refine or label the winner. See the "Research a strategy
end-to-end" workflow in MCP workflows.
Tool
Description
create_grid_template
Create a template from a strategy. kind picks the range shape and every mode is auto-clamped to the plan cap: zoom_in (default — narrow around current values), explore_higher / explore_lower (full window above / below), manual (legacy wide default).
list_grid_templates
List every grid template the caller owns
update_grid_template
Modify a template's parameter ranges before launch
delete_grid_template
Delete a template
check_variations
Return {count, limit} for a template — always call before create_grid
create_grid
Launch the grid; runs every variation, costs tokens beyond the daily allowance
list_grids
The caller's grids with filters. label, classification, root_ticker/timeframe/exchange, state, search, plus numeric filters. Two numeric shapes: operator suffixes<col>_<op> where col ∈ {sharpe, cumulative_return, max_drawdown, time_in_market, robustness_score} and op ∈ {gt, gte, lt, lte} — e.g. sharpe_gte=1.5, max_drawdown_gte=-0.15. Legacy aliasesmin_sharpe, max_sharpe, min_cumulative_return, max_cumulative_return, min_robustness_score, and max_drawdown (magnitude — 0.15 = "no worse than -15%") still work. Sort by robustness / sharpe / cumulative_return / max_drawdown / time_in_market.
get_grid
Grid detail: robustness verdict, ranked clusters (each with width + members), every variation's metrics
analyze_grid
(Re)compute the cluster analysis — used to backfill older grids; new ones analyse automatically
get_grid_suggestions
Proposed next searches from a finished grid — zoom_in inside the plateau + explore_higher/_lower above/below the tested range
refine_grid
Persist a chosen next-search as a new template; returns {template_id}. Follow with create_grid to launch
archive_grid
Hide a grid from the default list; reversible in the UI
set_grid_labels
Replace a grid's labels (free-form user-scoped tags, max 20 per grid, 32 chars each). Pass the full desired list; the call replaces rather than merges.
list_grid_labels
Autocomplete — every distinct label the caller has ever used
There are no proposal or promotion tools. Squads do not raise trades for
approval and have no autonomy tier — they publish a decision per covered
market, and strategies read it through the Committee Decision indicator. See
using a Squad in a strategy.