Skip to main content

GetActivityLog (Add-On Activity)

Returns the CrossTrade Add-On's recent activity log inside NT8. This is what the add-on prints to its Activity panel: connection events, signal routing, copier actions, opposing position protection, alerts, and warnings.

PropertyValue
Required scopemcp:read
RiskNone. Read-only.
Side effectsNone.

When an agent should use it

  • During trade copier diagnostics.
  • When investigating connection or reconnect issues.
  • When a webhook signal received an unexpected outcome.
  • During post-session audits.

When an agent should not use it

  • For tick-level data. The activity log is event-based.

Parameters

{
"from": "2026-05-15T13:00:00Z",
"to": "2026-05-15T22:00:00Z",
"level": "info",
"account": "APEX1234"
}

Level filters typically accept info, warning, error, debug. Admin-level events are gated; non-admin tokens see Info, Warning, and Hidden categories.

Response shape

{
"entries": [
{
"ts": "2026-05-15T14:32:10Z",
"level": "info",
"category": "copier",
"account": "APEX1234",
"message": "Leader fill received; follower routing started"
},
{
"ts": "2026-05-15T14:32:11Z",
"level": "warning",
"category": "copier",
"account": "APEX1235",
"message": "Follower rejected: max contracts reached"
}
]
}

Example user prompt

For APEX1234 and APEX1235 between 14:30 and 14:35 today, pull the add-on activity log.
Walk me through the timeline event by event and tell me why follower APEX1235 did not
match the leader fill. Do not show real account identifiers in the final summary.

Example tool call

{
"name": "GetActivityLog",
"arguments": {
"from": "2026-05-15T14:30:00Z",
"to": "2026-05-15T14:35:00Z",
"level": "info"
}
}

Common errors

SymptomLikely causeFix
Empty resultNo events in the range.Widen the time range.
Missing copier eventsCopier not configured.Check the trade copier docs.
addon_disconnectedAdd-on side is down.Open NT8.

Safe workflow placement

GetActivityLog → ListOrders → ListExecutions → GetSignalHistory → ListPositions

Correlate activity log entries with order timestamps. The activity log explains why the add-on did or did not act.