Tool calls
Logs → Tool calls records every tool call that runs through Workforce: succeeded, failed, redacted, or blocked. For the HTTP requests behind each call, see API request logs.
Fields on a tool call
The API calls tab on a call lists each request the Connector made to the third party. The same records come from GET /api/v1/logs/tool-calls/; see Stream logs to a SIEM.
Filter tool calls
Filter by employee, Connector, tool name, Tool Pack, status, date, request ID (exact match), or free text in request headers and the response. Filters combine.
Correlating with the model request
Two fields join a tool call to the model requests from the same prompt in LLM calls:
Claude Code sends traceparent only with OpenTelemetry tracing on, an otlp exporter, and CLAUDE_CODE_PROPAGATE_TRACEPARENT=1. The Workforce CLI sets this with mfw env. Codex CLI sends turn metadata on model requests only.
Debug a failed tool call
- Filter to the employee, tool, and time
- Read the error in the result JSON
- If the arguments are wrong, use a tool description override or tool input override
- If a field is missing, check Violations and alerts for the rule that redacted it
- Open the API calls tab:
401/403means the employee must reconnect the Connector,404means the resource is missing or inaccessible,429means a third-party quota
Tool call logs are kept for 90 days.