Logging tool calls and results in Agentic AI - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this logging command?

Given the following command to log a tool call and its result, what will be the output in the log file?

Agentic AI

log_tool_call('deploy', {'version': '1.2.3'})
log_tool_result('deploy', 'success')

A [ERROR] Tool deploy called with args: {'version': '1.2.3'}\n[INFO] Tool deploy finished with result: success

B [INFO] Tool deploy called with args: version=1.2.3\n[INFO] Tool deploy finished with result: success

C [INFO] Tool deploy called with args: {'version': '1.2.3'}\n[INFO] Tool deploy finished with result: success

D [INFO] Tool deploy called with args: {'version': '1.2.3'}\n[ERROR] Tool deploy finished with result: failure

💡 Hint

Look carefully at the log levels and exact argument formatting.

The logging function outputs info level messages with the exact dictionary of arguments and the result string as given.

❓ Troubleshoot

intermediate

Which option causes a logging failure?

Which of the following code snippets will cause a runtime error when logging tool calls and results?

A

log_tool_call('deploy', {'version': '2.0'})
log_tool_result('deploy')

B

log_tool_call('test', None)
log_tool_result('test', 'passed')

C

log_tool_call('build', {'target': 'release'})
log_tool_result('build', 'success')

D

log_tool_call('lint', {'files': ['a.py', 'b.py']})
log_tool_result('lint', 'completed')

💡 Hint

Check if all required arguments are provided to the logging functions.

Option A calls log_tool_result without the required result argument, causing a TypeError.

❓ Configuration

advanced

Which logging configuration enables detailed tool call tracing?

You want to configure logging to capture detailed tool call arguments and results with timestamps. Which configuration snippet achieves this?

A logging.basicConfig(level=logging.WARNING, format='%(asctime)s - %(message)s')

B logging.basicConfig(level=logging.ERROR, format='%(message)s')

C logging.basicConfig(level=logging.DEBUG, format='%(levelname)s: %(message)s')

D logging.basicConfig(level=logging.INFO, format='%(asctime)s - %(levelname)s - %(message)s')

💡 Hint

Detailed tracing needs info level and timestamps in the format.

INFO level with timestamps in the format string provides detailed logs with time and message level.

🔀 Workflow

advanced

What is the correct sequence to log a tool call and its result?

Arrange the steps in the correct order to properly log a tool call and its result.

A 1,3,2,4

B 2,1,3,4

C 2,3,1,4

D 1,2,3,4

💡 Hint

Logging the call happens before the tool runs, logging the result after it finishes.

First log the call, then run the tool, get the result, and log the result.

✅ Best Practice

expert

Which practice ensures reliable logging of tool calls and results in concurrent environments?

In a system where multiple tool calls happen concurrently, which practice best ensures logs are accurate and not mixed up?

A Use thread-safe logging libraries and include unique request IDs in each log entry

B Write logs to a shared file without synchronization to improve speed

C Disable logging during concurrent tool calls to avoid conflicts

D Log only the start of tool calls and ignore results to reduce log volume

💡 Hint

Think about how to keep logs clear and traceable when many things happen at once.

Thread-safe logging and unique IDs prevent log entries from different calls mixing and help trace each call separately.