Issue started today, where some of my tool calls request did not contain any arguments. Even when the tool properties are required. I saw there was some issues with tools lately but didnt know much how to fix this. Here is a callID: 14694c2f-4681-4f28-a8b5-a254da401406 And the toolID: 5403d2e1-a531-407e-893f-b05ef25ec7c9

Hi there! 👋 I see you're having issues with empty arguments in your tool calls. This is actually a known issue that's been reported recently, especially after some updates to the tool call system. Looking at your specific tool ID (5403d2e1-a531-407e-893f-b05ef25ec7c9), here are some troubleshooting steps you can try: 1. Check your configuration changes - Make sure no recent modifications have affected your tool calls or their arguments [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334114042876264518) 2. Review your completion messages configuration - Ensure that the configuration for tool call completion messages is correctly set [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334114042876264518) 3. Inspect Vapi logs - Look for any errors related to your specific call ID (14694c2f-4681-4f28-a8b5-a254da401406) [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341585041624666122) 4. Verify your function response format - Make sure responses follow this structure:

json
{
"results": [
  {
    "toolCallId": "your-tool-call-id",
    "result": "Your success or error message"
  }
]
}

[source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342188078437236916) 5. Check variable references - If you're using variable interpolation, ensure the syntax is correct:

json
{
"arguments": {
  "email": "{{start.output.email}}"
}
}

[source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1321375442644762625) If the issue persists, you can use the API to directly update messages for your specific tool: ```bash curl --location --request PATCH 'https://api.vapi.ai/tool/5403d2e1-a531-407e-893f-b05ef25ec7c9' \ --header 'Authorization: Bearer YOUR_TOKEN' \ --header 'Content-Type: application/json' \ --data '{ "messages": [ { "type": "request-complete",

Can you explain to me what changed exactly with the tools

I have also seen this issue, it just appeared out of nowhere

Ive been trying to isolate the issue, because not all my tool calls present that behaviour. For me, it seems that tool calls with specific a parameter was causing the issue. Removing this parameters from the tool made the assistant call the tool with the other arguments corerctly (instead of an empty argument array). The problematic parameter for me was the jwtToken, whis is a really long string like this: eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJuYW1laWQiOiIxMTU3ODg2IiwibmJmIjoxNzQwNjY5ODAxLCJleHAiOjE3NDA3NTYyMDEsImlhdCI6MTc0MDY2OTgwMX0.UgIpv6jICdCUO097PZHYXwciarx5nebCk29fid2pSTFhpqNjPFZ7AywTVdJuuheZiBQULfdPXl-UktxCZDxMbQ. Here was my tool parameters: "parameters": { "type": "object", "properties": { "jwtToken": { "description": "jwtToken provided in the Authentication Login response'", "type": "string" }, "appDateTime": { "description": "Start date & time of the appointment to book. The format is: 2024-11-27T11:30:00", "type": "string" }, "isAssessment": { "description": "Specify if the appointment is for an assessment (TRUE) or a followup (FALSE). ", "type": "boolean" }, "practitionerId": { "description": "Specific Id of the practitioner to look for appointment with ", "type": "number"

Your troubleshooting approach was correct - removing the JWT token parameter made the tool work with other arguments, confirming this parameter as the source of the issue. Token Reference Pattern: Instead of passing the full JWT token in the arguments, pass a reference ID and store the token elsewhere: FYI: Store sensitive tokens in environment variables and reference them by name.