Get a ticker's evidence pack for your own model
get_gambit_packThe evidence pack for one ticker, so YOUR OWN model can form a view of it (requires api:read). Optional: Gambit already keeps your view on its side from the facts you add; use this only when the user wants their own model's view. 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. Returns based_on_version (the shared version the pack is built from), pack (the shared take with everything behind it: its levers with state, what is priced and thresholds, its tests with watch ids, macro, mechanics and the analyst's ledger; the market numbers; and items, each with its item_id: the sources the shared take rests on, plus your own facts marked kind user with negative ids), rules (Gambit's analyst method; items marked kind user are the user's own information: assume they are true and say so), output_schema (the JSON schema of the take to return) and submit_with (submit_gambit_view). Gambit runs no model for this call. Next: form the take with your model, following the rules and output_schema, cite only ids from this pack (the item_ids of items, and the ids the shared take itself cites, which can be older than items), and pass the JSON object to submit_gambit_view with your model's name and this pack's based_on_version. 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); 503 gambit_reads_disabled while these reads are 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>"
},
"name": "get_gambit_pack"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |