Unable to get arguments in the request body of ser...
# support
s
Hi this is urgent !!! I a unable to get arguments in server url body when a tool call is initiated. Refer this call ID '0199e444-ffde-7aa9-96ff-7451239af94d'. At aroung 4:53 it initiated tool call to send email and it failed, when i checked i found that no arguments came in the server url. Please check this asap.
v
It sounds like your tool's parameters may not be defined correctly, which can cause arguments to be missing in the server URL body. Make sure your tool configuration includes a
parameters
section like this:
Copy code
json
"parameters": {
  "type": "object",
  "properties": {
    "emailAddress": { "type": "string", "description": "Recipient's email" },
    "message": { "type": "string", "description": "Email content" }
  },
  "required": ["emailAddress", "message"]
}
Update your tool's parameters and test again—this should ensure arguments are sent in the tool call payload. [See more in the Vapi documentation](https://docs.vapi.ai/server-url/events) Sources: - [Server events](https://docs.vapi.ai/server-url/events) - [Debugging](https://docs.vapi.ai/debugging)
s
Hi @Vapi team pls check asap
hello team @Vapi @Shubham Bajaj could anyone pls help me to figure out this issue ?
c
Thank you for the call id. We are reviewing the details of your request and will reach out to you when we have an update or if we need additional information.
s
can i expect a response soon as this is reported by customers and we need to answer them soon
c
We noticed you are using GPT-4.1-mini as the LLM, which may produce inaccurate results. Please switch the model to GPT-4.1 or GPT-4o to check if arguments are sent with the tool call
s
i tried using 4o and it threw the same issue refer callid id : 019a0698-5c7f-733e-8322-0921e5d158ae around 3:58 it made tool call and it failed the reason is same no arguments came in the tool call payload. Please ask it to developer team and get confirmed is it something i need to turn off any parsing or something on my end, let me know whatever i need to do on my side but i am in urgency need to address the clients
019a06a5-ec70-733e-832a-7dfbb606f666 here used 4.1 the issue is same
019a0aac-cd5b-7aaa-bc0e-1ff8aaffc64a Hi one more call id here
@Shubham Bajaj @User @Kyle please look into this urgently. I suspect this could be maybe some parsing techniques used by vapi. Let me know if i can turn off
THIS IS URGENT !!!!! @Vapi
or maybe some max tokens issue for tool calls ?
could anyone please help me investigate ???
hello @Vapi team any updates ????
@Shubham Bajaj @User
Hello @Vapi team just following up again to check if any updates on this issue ?
Good morning @Vapi team Did we get any chance to look into this >
Morning @User anyone up and looking into the issue. Could you please acknowledge ?
Morning @Vapi team @Kyle any updates ??
I’m very disappointed with the kind of support provided by the @Vapi team. It’s been weeks, and there’s still no solution .... in fact, there hasn’t even been any acknowledgment. This really affects my confidence and interest in continuing to work with Vapi. Please let me know if I’m wrong
REOPEN
c
Hi Sahil, Apologies for the delay here — and thank you for your patience. We’ve reopened your ticket and reviewed the logs for the call ID you shared. We can confirm that the arguments were correctly passed into the LLM, but were not forwarded to your tool call, which explains why the request body was empty on your end. We’ve now notified our engineering team to investigate this behavior further. We’ll follow up as soon as we have an update or need additional details from you. Thank you again for flagging this and bearing with us.
s
I hope it gets fixed before next year 🙂
c
Could you try testing a call with your tool with your parameters? There have been some updates to the platform and I just want to confirm if this issue is still present.
2 Views