[
https://issues.apache.org/jira/browse/CAMEL-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892444#comment-17892444
]
Bruno Meseguer commented on CAMEL-21355:
----------------------------------------
I agree... connecting two different components will overcomplicate things.
To be honest, because no-tool calling is a valid scenario for the LLM I
wouldn't throw an exception. I don't even see the need to define a parameter
switch between throw/ignore the no-tool response (because it's valid).
I would simply look at cases where the tool call from the LLM is mal-formed to
throw an exception from Camel, or when any other non-expected error occurs when
interacting with the LLM.
What do you think?
> LangChain4j Tools fails with direct LLM response
> ------------------------------------------------
>
> Key: CAMEL-21355
> URL: https://issues.apache.org/jira/browse/CAMEL-21355
> Project: Camel
> Issue Type: Bug
> Components: camel-langchain4j-tools
> Affects Versions: 4.8.0
> Reporter: Bruno Meseguer
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> The Tools component is designed to provide functions to the LLM. However the
> LLM may decide not to invoke any of the given tools.
> In that scenario, the LLM replies directly instead of requesting the
> execution of a tool/function. The Camel Tools components seems unable to
> handle such use case and throws an exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
