[
https://issues.apache.org/jira/browse/CAMEL-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892428#comment-17892428
]
Otavio Rodolfo Piske commented on CAMEL-21355:
----------------------------------------------
I think adding an option to throw/no-throw is a reasonable compromise and give
the users some flexibility. Maybe allow them do define some bean to handle?
Maybe just cascade the response? What do you think [~bruno.meseguer] ?
At this point, I'd prefer to avoid more complex scenarios involving adding
other components as dependencies and try to favor something that can be
flexible and simple (not saying, never, though ... just trying to minimize the
scope of the fix).
> 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)
