Plan a trade from your own limits (places nothing)
plan_gambitThree timeframe alternatives (LTF hours–days, MTF days–weeks, HTF months–years), with optional timeframe/source_version selection and private entry/stop/target refinement. Refined sizing is recalculated; no orders are placed. A trade plan for one ticker from YOUR own limits (requires api:recommend) — the call for "how would I size this?". The chain for one ticker. Everything it stores is in YOUR personal layer: the shared view never changes because of it. Gambit forms your view on its side: you do not need your own model for it. (1) Add data: add_gambit_evidence stores a fact you know. It is labelled unconfirmed until Gambit confirms it from an official or wire source that states it; a confirmed fact's source joins the shared evidence, and the shared view uses it on its normal run. (2) Your view: your own take, which Gambit keeps for you. It starts as the shared take. Each fact you add, each new shared version and each update you ask for moves it: Gambit's per-story step judges your new facts and the shared news since your last update against your take and applies its verdicts. A fact that changes a lever adds a test to your take: wrong if the fact is not confirmed by its check-by date. A fact that expires unconfirmed after its check-by date leaves no trace: when Gambit had set it aside (it moved nothing), your view stays as it is; otherwise your take points back to the shared take and Gambit applies your remaining facts again on it, and with no fact left you follow the shared view. remove_gambit_evidence takes one fact back; reset_gambit_view takes back every fact. When your take ends up the same as the shared one, you follow the shared view again. To use your own model's view instead (optional): call get_gambit_pack, form the take with the rules and output_schema in the pack, then call submit_gambit_view; Gambit then moves that view the same way. (3) What if: what_if_gambit gives the view if something happened; when the question matches a dated condition the view already lists, the answer is precomputed and no model runs; otherwise it returns the pack with the event added, for your model to answer. (4) Plan: plan_gambit gives entry, stop, size and exits from your own limits. A plan is not a recommendation to trade and places no order. use: shared (plan from the shared view) or mine (plan from your latest accepted view while get_gambit still shows it; the answer also gives the size from the shared view, so the difference your view makes is explicit: differs.line says "With your information" for a view Gambit formed from your facts, and "With your view (formed by )" for one your own model formed). risk_pct (optional): the percent of the account to risk; by default your trade policy's, else Gambit's default. account_value (optional, USD): Gambit does not read it from your portfolio; without it the plan has no size (size_usd null, and needs lists account_value), so ask the user for it. The direction follows the view's lean. With no real lean (|shown_lean| below 1) the answer is action no_trade, with why. Otherwise: entry (the latest price), stop (from the ticker's realized volatility), size_usd and risk_usd (sized so that a stop-out loses about risk_pct of the account; capped_by_max_position is true when your maximum position size cut it, and capped_at_account_value when the size stopped at the whole account value, so risk_usd is then less than risk_pct), exits (the view's dated "wrong if" conditions, plus the stop), check_by (the earliest confirm-by date of your facts), based_on, limits_used, differs and disclaimer. Price levels belong to the plan, never to the view. Tell the user it is a plan from their own limits and not a recommendation to trade. It places no order, writes no trade record, runs no model and uses no recommendation quota; the plan is kept in your personal layer (plan_id), and a daily limit applies (429 rate_limited with retry_after). Errors: 409 gambit_building when Gambit has no view of the ticker yet (get_gambit by symbol queues it; try again later); 404 unknown_symbol; 422 ambiguous_symbol with candidates (call again with one candidate as the symbol); 409 no_user_view when use is mine and you have no current accepted view (add data or submit a view again); 409 price_unavailable or volatility_unavailable when the plan cannot set its levels; 503 gambit_personal_disabled while the personal layer is switched off.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"symbol": "<symbol>",
"use": "<use>"
},
"name": "plan_gambit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| use | Yes | shared: plan from the shared view; mine: from your latest accepted view | |
| symbol | Yes | a ticker such as BTC or NVDA, or an exact id such as xyz:GOOGL or ref:eq:IP, as for get_gambit | |
| risk_pct | No | percent of the account to risk on this plan | |
| timeframe | No | Select a timeframe; all alternatives remain in the response | |
| refinement | No | ||
| account_ref | No | Only manual account inputs are currently supported; this is not a connected-account selector | |
| account_value | No | account value in USD | |
| source_version | No | Required with timeframe; accepted shared version being selected | |
| source_user_view_id | No | Required when selecting from mine; pins the private view identity |