https://vapi.ai/ logo
Join Discord
Powered by
Tool calling argument names are not consistent
# support
k
v
@kmskrishna I'm sorry to hear that you're experiencing inconsistencies with the VAPI tool. To better assist you, could you please provide me with more details about the issue? Specifically, what are the "_s" you're referring to? Are you experiencing intermittent issues with certain voice commands or API responses? Any additional information you can provide will help me understand and address the problem more effectively.
You can continue this conversation by mentioning me in the message.
k
No of People is the argument name no_of_people is the another argument name in two differnt calls it changed
One difference is that one was done by calling the number and one was triggered using Vapi dashboard talk to assistant feature.
After a little more testing, noticed that when calling from mobile the function arguments in the tool call has _'s. eg: no_of_people where are when doing web call, they are exactly how it is in the frontend. "No of People"
s
It's because of your prompting and tool description please check it again to ensure everything is correct.
for more check our prompting guide: https://docs.vapi.ai/prompting-guide
k
Everything is correct.
I hope I was able to convey my problem.
how to solve this issue?
@Vapi
v
@kmskrishna It seems like there might be a discrepancy in how the argument names are being processed or formatted between calls made from the mobile and web interfaces. This could be due to the way the VAPI tool handles input from different sources, possibly involving a conversion or normalization step that is not consistently applied. To address this issue, you might want to ensure that the argument names are handled uniformly across all interfaces. This could involve updating the VAPI tool's code to standardize the argument names, regardless of the source of the call. If you have access to the backend code, you could implement a function to convert all argument names to a consistent format (e.g., always using underscores or always using spaces). If you do not have access to the backend, you may need to reach out to the VAPI support team or consult the documentation for guidance on how to ensure consistent argument naming. Since you've mentioned that everything is correct according to the prompting guide and the tool description, it might be a more intricate issue that requires direct support from the VAPI team. You can contact them with the details of your findings, and they should be able to provide a more specific solution. If you believe the issue has been sufficiently conveyed and you'd like to close this support ticket, please let me know, and I can proceed with that. If there's anything else I can assist you with, feel free to ask.
s
your problem is conveyed, can you share the call id.
k
call_JHG4Pm9l1V3xRyFQPErw4C9K
call_L7OlsTIxlmxadXim3f7q2imc
s
this is not call id. gio to vapi dashboard > call logs > copy call id.
k
27aabf34-7944-4952-b645-65d77f44c20e
989c35ab-21d6-421a-a731-b863de1b3c21
s
Add the tool 
BookTable
to your assistant and follow the Vapi prompting guide it will work.
Also for tools descripption make it combination of usage, description, purpose, expected input parameters and optional output in 160 characters to have highest chances of calling the tool awlays.
k
The tool is always being called.
it is not the issue,
the issue is the parameter names that i am getting is not consistant on web calls and phone calls.
s
adding the tool description as said above will always pass the expected input parameters in expected strucutered format.
2 Views
PreviousNext
Powered by