Strategy Counters
tt_get_strategy_countersThe runtime variables (counters) a deployed strategy is holding now.
This is what a trader means by "the counter" — the values the engine
carries as the strategy runs: a remembered entry price
(entry_px_s3_l1), a regime flag, a rotation pick. Each comes with the
run it belongs to and when it last changed.
USE WHEN the user asks what a strategy "remembers", what its entry price was, why a condition has or hasn't fired, or wants to see its state mid-run. Pairs well with tt_diagnose_strategy: diagnosis says what happened, counters say what the strategy is currently holding.
Args:
strategy_id: the DEPLOYED strategy id (SID) from
tt_get_my_deployed_strategies — NOT a template id.
name_prefix: optional filter, e.g. "entry_px" or "rfm_pick".
Matched case-sensitively at the start of the name.
changed_only: True drops the variables still at zero and
untouched since the run began. On a grid
deployment that is most of them — 88 of 153 — and
the full list runs to 42,000 characters. The
response always reports n_moved and
n_zero_since_run_start either way.
An empty list is usually normal, not a fault — it means the strategy has not entered yet this run, or keeps no state. Say that rather than implying something is wrong.
Read-only, and available for live deployments as well as Live Offline — seeing your own numbers changes nothing.
AUTH-REQUIRED, and ownership-gated: a SID that isn't the user's is refused.
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": {
"strategy_id": "<strategy_id>"
},
"name": "tt_get_strategy_counters"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name_prefix | No | ||
| strategy_id | Yes | ||
| changed_only | No |