Skip to content

Tool Call Reasoning Example#19232

Open
igordayen wants to merge 1 commit into
eugenp:masterfrom
igordayen:tools-selection-reasoning
Open

Tool Call Reasoning Example#19232
igordayen wants to merge 1 commit into
eugenp:masterfrom
igordayen:tools-selection-reasoning

Conversation

@igordayen

Copy link
Copy Markdown

OVERVIEW

  1. Developed ToolCallReasoningIntegrationTest.java for Blog "LLM Tool Call Reasoning Using Embabel Agentic AI Framework"
  2. Updated parent pom.xml
  3. Added README.md

@igordayen

Copy link
Copy Markdown
Author

I see build suddenly failed now, however, not able to see details, please advise, thanks

@theangrydev theangrydev left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please apply the Baeldung formatting code style:
https://github.com/Baeldung/dev-settings/tree/main/javaCodeStyle

* - Whether thinking blocks accumulate correctly in both scenarios
*/
@Test
void parkingDecisionMakerWithMultiProbes() {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please follow the guidelines regarding BDD test names, the format should be either

givenXxxYyy_whenXxxYyy_thenXxxYyy
whenXxxYyy_thenXxxYyy

* - Whether thinking blocks accumulate correctly in both scenarios
*/
@Test
void parkingDecisionMakerWithMultiProbes() {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test is very verbose and reads more like a demo script than a real test, relying mostly on logging and conditional sections that I wouldn't usually expect to see in a test - was this intentional?

There is also no separation between test code and production code - I can't easily tell which parts are the "system under test" vs which parts are only the test harness

Comment on lines +54 to +58
<configuration>
<source>21</source>
<target>21</target>
<release>21</release>
</configuration>

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are these being set both here and in the properties section?

Comment on lines +2 to +3
*
*

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove blank lines (same elsewhere)

}
}


Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove blank lines (same elsewhere)

*
* <link>https://github.com/embabel/embabel-agent-experimental/blob/main/embabel-experimental-integration-tests/src/test/java/com/embabel/agent/api/tool/loop/thinking/ToolCallReasoningIT.java</link>
*
* Original code (see link above)) was developed by Embabel Pty Ltd, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have permission to reuse this without a license? The original license in the linked file is Apache, so I would expect to see the license header and reproduced, and a copy of the Apache license included

More typically, the IP used in Baeldung is usually original work - is there any reason you did not write an original example for Baeldung and chose to adapt existing work?


@LlmTool(description = "Reserve guaranteed garage parking near destination.")
public String reserveGarage(String location) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove blank lines at the start of methods (same elsewhere)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants