Add tool call parameters for on_tool_start hook
#253
Conversation
| ( | ||
| agent.hooks.on_tool_start(context_wrapper, agent, func_tool) | ||
| agent.hooks.on_tool_start(context_wrapper, agent, func_tool, tool_call.arguments) | ||
| if agent.hooks |
There was a problem hiding this comment.
Since using only arguments as a parameter is too granular, and adding tool_call.id in the future would lead to parameter inflation at the root level, plus tool_call.id is actually needed, would it be better to pass the entire tool_call object as a parameter instead?"
There was a problem hiding this comment.
@mini-peanut Thanks for your review! I've updated the hook to use Action, which not only includes the Tool but also contains the instance information for a tool call, including the parameters and tool_call.id.
|
@yanmxa thanks for doing this work, very useful! |
4724b5e to
c3287fd
Compare
|
much needed feature! |
|
I learned that if you use Example: result = Runner.run_streamed(
agent,
input,
)
async for event in result.stream_events():
if event.type == "run_item_stream_event":
if event.name == "tool_called":
print(
f"-- Tool {event.item.raw_item.name} was called with args: {event.item.raw_item.arguments} "
)
elif event.name == "reasoning_item_created":
summary = event.item.raw_item.summary
# there’s at least one summary part
# o-series models will send this every response, it is sometimes blank
if summary:
text = summary[0].text
print(f"-- Reasoning item created: {text}")
print("--")
elif event.name == "message_output_created":
print(event.item.raw_item.content[0].text)
else:
pass # Ignore other event types |
Resolve: #252