Deployed Strategy Detail
tt_get_my_deployed_strategy_detailDeep read on ONE of the signed-in user's deployed strategies — the tool for "why is my strategy in error / blocked / stuck?". Returns its current status, recent event log (the human-readable reason it halted or errored), the broker connection it trades through, and recent orders (a rejection carries the broker's reason). AUTH-REQUIRED.
strategy_id is the numeric id from tt_get_my_deployed_strategies — if
the user names a strategy ("my abc strategy"), call that tool first to
resolve the id, then call this. Reasoning over the returned status +
events + orders is up to you; the data is scoped to the caller (another
user's id returns not-found).
Two things the rows do not say themselves. recent_events is mostly
Status Change entries — they record a state move, not what the
strategy did, they name no order or condition, and several share one
whole-second timestamp, so their returned order is arbitrary and will
not always chain: read status for the current state, never the last
event. And an order row with broker_order_id null carries no broker
execution record at all — on a LIVE-OFFLINE deployment (no order is
placed there) that is every row, and status "Initiated" with
executed_quantity 0 is where they stop for good, not a stuck order.
The response's orders_caveat and events_note carry both in full
when they apply.
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_my_deployed_strategy_detail"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| strategy_id | Yes |