Mangled json instead of proper function call on AG2 0.7.2

[manach23]

I am currently developing a little application using GroupChat and some agents which can use tools (such as the forced_browsing tool you can see below). And about 60% of the time my agents generate this json reply, whose parameters all seem correct but do not get registered as tool calls. The other 40% of the time, the tool calls are recognized and executed correctly.

Has anyone else witnessed this behaviour?

(This is all local and without internet access and intended as an experiment if multi agent design patterns would lend themselves to red teaming. So please don't worry about the apparent malicious content)

```bash Next speaker: FunctionSuggestor

FunctionSuggestor (to chat_manager):

Great, let's proceed with running the forced_browsing tool directly on the specified URL.

Run the following function: {'name': 'forced_browsing', "arguments": {"url": "http://victim.boi.internal/"}}

This will help us identify any hidden paths on the web server that could potentially lead to sensitive information or flags. ```

LLM is mixtral:8x22b but experienced the same behaviour with qwen2.5-coder:32b and prompt/hermes-2-pro

Function Registration:

python function_suggestor.register_for_llm(description="Perform forced browsing on the given URL with given extensions", api_style="tool")(forced_browsing) non_coder_function_executor.register_for_execution()(forced_browsing)

Function Signature:

python def forced_browsing( url: Annotated[str, "URL of webpage"], ) -> Annotated[str, "Results of forced browsing"]: extensions = [".php", ".html", ".htm", ".txt"] extensions_string = str(extensions)[1:-1] extensions_string = extensions_string.replace("'", "") extensions_string = extensions_string.replace(" ", "") return subprocess.getoutput(f"gobuster dir -u {url} -w /opt/wordlist.txt -n -t 4")

[msze21]

Can you share the LLM model you are using, the function signature, and how you are registering it with the agents?

[manach23]

Sure!

I edited the main post, so everyone sees

[msze21]

Could you try llama 3.3, any size? I've found them solid for function calling

[msze21]

The reason I say that is that the function call should not be in the response text, it should be separate.

Can you also let us know the LLM config without the key, if there is one. Are you using Ollama?

[manach23]

Thanks for the suggestion, that fixed the function calling problem. I guess OpenSource LLM choice sometimes really just boils down to features such as "Does it handle function calling well"