Hello. I previously submitted a PR to ollama4j and it was merged, but I don't think I can just wait for it to be released. I also DM'd @wenjin for advice earlier, it seems like I could hack it by overriding specific methods in Ollama4j. This approach enables the use of Flink agents' ToolCallAction components like ToolCallRequest and ToolCallResponse. (I tested this with the latest commit.) What are your thoughts? Thank you.

Hey there. Just curious, but what is the use case? What are you looking to use this for?

Hi, you can follow up via this PR https://github.com/apache/flink-agents/pull/162

@hope One possible approach I see is to wrap the tools before register them to the ollama4j. In this way, ollama4j will call the wrapped methods, where we can leverage the built-in ToolCallAction to actually call the tools. I think this might be more reliable compared to just overriding the ollama4j internal methods. However, I'm not entirely sure how necessary is this complexity. The only problem of having tools called by ollama4j is that, they do not appear in our event logs. From my perspective, this might be something we can temporal live with in the first mvp release. So I was considering just wait for the new release of ollama4j. Any specific reason that you can't wait for the ollama4j new release?

@Xintong Song Hello. Thank you for your response. I can wait long enough, but I don't know when the new release of ollama4j will come out. I will ask the maintainer of ollama4j directly. Thank you.