Open qianheng-aws opened 3 weeks ago
7. In debug mode, you will see the input of PPLTool will be overridden by the input of MLModelTool.
Do you mean the input of PPLTool should actually be the output of MLModelTool?
- In debug mode, you will see the input of PPLTool will be overridden by the input of MLModelTool.
Do you men the input of PPLTool should actually be the output of MLModelTool?
Closely, it should be its own input { "question": "${parameters.MLModelTool.output}"} with placeholder substituted. It means the output of MLModelTool is been put in value of question.
The reason why I don't use the output of MLModelTool directly is that PPLTool cannot handle the output. Otherwise, we may need to develop other tools to parse the output to what exactly PPLTool can accept, or enhance flow agent to do similar things.
What is the bug? If we create an AgentTool containing several tools and some tool may have their own input parameter, when ChatAgentRunner selects this AgentTool to execute, it will generates its input parameter passing to the first tool of AgentTool. However, this input parameter will also override the default manual input parameter of following tools. We should not let it to override since it's only for the input parameter of the first tool.
How can one reproduce the bug? Steps to reproduce the behavior:
Register an flow agent with 2 tools like:
What is the expected behavior? The input of PPLTool should be our manual set input
{ "question": "${parameters.MLModelTool.output}"}
with placeholder substituted.What is your host/environment?
Do you have any screenshots? If applicable, add screenshots to help explain your problem.
Do you have any additional context? Add any other context about the problem.