The activity log
Access rules describe what Alma may do. The Log tab shows what it did.
Each row is one tool call through this connection: the tool name, its origin, whether it succeeded, and when.
Where a call came from
| Shown as | Means |
|---|---|
| The workflow’s name | A workflow run |
| Chat | Someone talking to Alma |
| Agent | An agent acting outside a named workflow |
| MCP client | An external client, over MCP |
| API | A call through the public API |
| Briefing | A scheduled briefing |
This log covers every channel, not just MCP. To audit external MCP clients specifically, use MCP → Usage.
Filtering
Search by tool name, then narrow by time window, tool, or result (Any result / Succeeded / Failed). Filter to Failed in the last hour to check whether something actually went through.
Empty state
A connection with no activity shows: “No activity yet — tool calls appear here once Alma uses this connection.”
If you expected activity and see none, check that the relevant workflow is enabled — a draft never runs.
If the tab says tool controls and activity aren’t available, that usually means the connection exposes no toolkit — but the same message can appear on a transient query error. Reload before concluding it doesn’t.
Workspace-wide changes
For changes to your configuration — a topic edited, an outcome archived, a workflow paused — see Activity instead. The Log tracks tool calls through one connection; Activity tracks changes across the workspace.