I am encounter this error: " tool-calls Server URL Error: Request failed with status code 400". But, my API endpoint is working correctly. This only happens when I directly put my server URL endpoint in the tool description and the tool type is "function". But, the workaround is to create a tool with type set to "make", then create a webhook in a make scenario to process the parameters into my application by using HTTP post to the exact same server URL endpont. I notice the tool call always pass the whole JSON object comprising of the assistant properties, toollist, customer and a lot of stuff. My API endpoint just needs the function parameters in a JSON format, that's all. Note, in both case, the HTTP response format is the same as expected by VAPI. So, why does it work If I go through Make, but fails when called directly. I can't imagine changing my API to expect the whole request payload that VAPI is sending over, too much processing required to find the tool and it's parameters to extract. Is it how everyone is doing it? When I use Make scenario, I use Create JSON and Parse JSON to process the tool parameters into the correct format before calling HTTP module to post the data to my endpoint. But imagine the cost involved for using a third-party application to reduce the payload to just a few parameters, when I should directly call my endpoint from VAPI and receive the payload I ONLY defined. ElevenLabs does this perfectly and my application works from there. But, I prefer to use VAPI because it is much bigger platform with more capabilities. So, I want to cut out the cost of using Make to process the payload before calling my API. Instead, I want to directly call my API from VAPI and ONLY receive the parameters I defined in the tool. Thanks,