GetSignalHistory (Webhook Signals)
Returns CrossTrade's history of TradingView webhook signals. The agent can correlate webhook payloads to add-on activity, orders, and executions to explain what happened to any signal.
| Property | Value |
|---|---|
| Required scope | mcp:read |
| Risk | None. Read-only. |
| Side effects | None. |
When an agent should use it
- During webhook diagnostic workflows ("why didn't this signal fill?").
- During strategy decay reviews.
- In a daily session audit for automated webhook strategies.
When an agent should not use it
- To replay or resend signals. This tool does not replay.
Parameters
{
"from": "2026-05-10T00:00:00Z",
"to": "2026-05-16T23:59:59Z",
"limit": 100,
"account": "Sim101"
}
Some fields may be optional depending on add-on version. The default range is recent activity.
Response shape
{
"signals": [
{
"received_at": "2026-05-15T14:32:11Z",
"source": "tradingview",
"payload": { "action": "buy", "instrument": "MES", "qty": 1 },
"match": {
"command": "place_market",
"account": "Sim101",
"order_id": "abc-321"
},
"outcome": "filled",
"notes": ""
}
]
}
Example user prompt
Pull the last 24 hours of webhook signals for Sim101. For each signal, tell me the
intended action, whether it matched an order, and the final outcome. Highlight any
that did not fill, including the likely reason. Redact account identifiers in the
summary.
Example tool call
{
"name": "GetSignalHistory",
"arguments": {
"from": "2026-05-15T00:00:00Z",
"to": "2026-05-16T00:00:00Z",
"limit": 100,
"account": "Sim101"
}
}
Common errors
| Symptom | Likely cause | Fix |
|---|---|---|
| Empty result | No signals in the range. | Widen the range. |
| Missing match | Payload was malformed or mapping failed. | Read the payload and check the webhook docs. |
addon_disconnected | Add-on side is down. | Open NT8. |
Safe workflow placement
GetSignalHistory → ListOrders → ListExecutions → ListPositions
The agent should correlate the timestamp of the signal with the order activity in NT8 to explain misses.