Heuristic required tool choice

[antoniibelyshev]

Motivation and Context

Models without the tool choice capability (e.g. most of the ollama models) cannot rely on the toolChoice in the model api. This makes some workflows inconsistent, in particular, subgraphWithTask does not work with such models since it relies on the toolChoice parameter. This pr introduces a workaround for this issue using LLMBasedToolCallFixProcessor, which now will use prompts to force LLM to generate a tool when the toolChoice is set to Required.

Breaking Changes

---

Type of the changes

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tests improvement
• Refactoring

Checklist

• The pull request has a description of the proposed change
• I read the Contributing Guidelines before opening the pull request
• The pull request uses develop as the base branch
• Tests for the changes have been added
• All new and existing tests passed

Additional steps for pull requests adding a new feature

• An issue describing the proposed change exists
• The pull request includes a link to the issue
• The change was discussed and approved in the issue
• Docs have been added / updated

[github-actions]

Qodana for JVM

1257 new problems were found

Inspection name	Severity	Problems
Check Kotlin and Java source code coverage	🔶 Warning	1237
Missing KDoc for public API declaration	🔶 Warning	20

@@ Code coverage @@
+ 72% total lines covered
18184 lines analyzed, 13157 lines covered
# Calculated according to the filters of your coverage tool

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions