You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: stage_descriptions/base-03-md6.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ When you detect a `tool_calls` array in the response:
51
51
2.**Parse the function name**: Read the function name to determine which tool to execute.
52
52
3.**Parse the arguments**: Parse the function arguments as a JSON string to get the parameters.
53
53
4.**Execute the tool**: Your program must perform the action requested. For the `Read` tool, use your language's file system library to read the file at the requested `file_path`.
54
-
5.**Output the result**: Print the tool execution result. For the `Read` tool, print the raw file contents to stdout.
54
+
5.**Output the result**: Print the tool execution result. For the `Read` tool, print the raw file contents directly to stdout (just the contents, with no labels or formatting).
55
55
56
56
In previous stages, you printed the message content directly to stdout. Now that the model's response can include tool calls, you should **only print the message content if there's no `tool_calls` array** in the response.
0 commit comments