fix:toolcall return string

[Cui-xf]

Signed-off-by: Cui-xf cui_xf293@qq.com

Thank you for taking time to contribute this pull request!
You might have already read the [contributor guide][1], but as a reminder, please make sure to:

• Sign the contributor license agreement
• Rebase your changes on the latest main branch and squash your commits
• Add/Update unit tests as needed
• Run a build and make sure all tests pass prior to submission

[markpollack]

the current assumption is that if is not a rendered image, we assume it is json (also a string) in this current PR, the json conversion in the else statement will never be accessed. Can you explain more of the surrounding use case that motivated you to make this change? adding to DefaultToolCallResultConverterTests?

[markpollack]

Also wondering why JsonParser.toJson(result); doesn't use Type returnType

[markpollack]

any thoughts @tzolov ?

[Cui-xf]

the current assumption is that if is not a rendered image, we assume it is json (also a string) in this current PR, the json conversion in the else statement will never be accessed. Can you explain more of the surrounding use case that motivated you to make this change? adding to DefaultToolCallResultConverterTests?

Hey, thanks for the review!
I noticed that when I use the org.springframework.ai.tool.annotation.Tool annotation and the method returns a String, the result gets escaped (see screenshot below). I’m not really sure if this is the expected behavior, or if there’s any doc about it.
If this is actually, I will to close the PR.
Thanks!

[tzolov]

@Cui-xf this is an interesting case:

Currently the DefaultToolCallResultConverter assumes that all string values are of type JSON (including) the string literals.
Note that "Foo Bar" is not JSON but toJson("Foo Bar") converts it into a valid json: ""Foo Bar"".

Here is an example how the DefaultToolCallResultConverter behvaves:

public class Main {

    private static final ObjectMapper OBJECT_MAPPER = JsonMapper.builder().build();

    public static void main(String[] args) {

        var value1 = "Foo Bar";
        System.out.println("Value 1: " + value1);
        System.out.println(String.format("- raw value: %s, is JSON: %s", value1, isValidJSONJackson(value1)));
        System.out.println(String.format("- toJson(value): %s, is JSON: %s", toJson(value1),
                isValidJSONJackson(toJson(value1))));

        var value2 = "{\"hello\": \"world\"}";
        System.out.println("Value 2: " + value2);
        System.out.println(String.format("- raw value: %s, is JSON? %s", value1, isValidJSONJackson(value2)));
        System.out.println(String.format("- toJson(value): %s, is JSON? %s", toJson(value2),
                isValidJSONJackson(toJson(value2))));
    }

    public static boolean isValidJSONJackson(String jsonString) {
        try {
            OBJECT_MAPPER.readTree(jsonString);
            return true;
        } catch (Exception e) {
            return false;
        }
    }

    	public static String toJson(@Nullable Object object) {
		try {			
			return OBJECT_MAPPER.writeValueAsString(object);
		}
		catch (JsonProcessingException ex) {
			throw new IllegalStateException("Conversion from Object to JSON failed", ex);
		}
	}
}

Would generate:

Value 1: Foo Bar
- raw value: Foo Bar, is JSON: false
- toJson(value): "Foo Bar", is JSON: true

Value 2: {"hello": "world"}
- raw value: Foo Bar, is JSON? true
- toJson(value): "{\"hello\": \"world\"}", is JSON? true

Before we try to change the default behavior perhaps you can try to implement a custom ToolCallResultConverter implementation?
https://docs.spring.io/spring-ai/reference/api/tools.html#_result_conversion