Hi is there a limit to the size of the tool call arguments used? I have the following call where the tool is called with empty args despite the tool definition specifying required params and

strict

being set to

true

- call ID:

e6c592bb-18c5-4e9b-9840-98854a1b2b78

- timestamp:

2025-04-21T17:17:28.563Z

to

2025-04-21T17:21:30.928Z

- response expected:

{
  "role": "tool_calls",
  ...
  "toolCalls": [
    {
      "id": "call_37PkgM0scJ85xzcVrZv8bqUX",
      "type": "function",
      "function": {
        "name": "searchForOpenSlots",
        "arguments": ""{\"practiceIds\":[\"019321ae-72e8-7fec-a19f-b57edc9d2ccb\",\"019321ae-72e9-7a77-b2f5-0895209479f0\",\"019321ae-72e9-7af6-8c3c-fcf3412262ca\"],\"providerIds\":[\"0193ad11-1d74-718d-b1cf-cf40ca5cccd3\",\"0193ad11-1d76-79aa-a6d1-0b9e820f0fbc\",\"0193ad11-1d79-71ec-8d41-885961dcf190\",\"0193ad11-1d7b-7a14-a12f-d5e8ab18f97c\",\"0193ad11-1d70-790e-b83f-afab757e8896\",\"0193ad11-1d94-7873-b902-19785c6df6c6\"],\"appointmentTypes\":[\"SCRN_MAMMO_BILATERAL_TOMO\"]}""
      }
    }
  ],
}

- response received:

{
  "role": "tool_calls",
  ...
  "toolCalls": [
    {
      "id": "call_37PkgM0scJ85xzcVrZv8bqUX",
      "type": "function",
      "function": {
        "name": "searchForOpenSlots",
        "arguments": "{}"
      }
    }
  ],
}

Hi there! I've looked into your issue with the empty tool call arguments despite having required parameters and

strict: true

, but I need to escalate this to our technical team for a deeper investigation. Based on our documentation, there are several potential causes for this behavior: - The

strict

parameter might not be correctly passed to OpenAI models in some cases - There could be issues with variable referencing or interpolation in the tool call - The function schema might be missing

additionalProperties: false

I've shared all the details you provided (call ID, timestamps, expected vs. actual response) with our engineering team. They'll need to check the logs and configuration for your specific case to determine exactly what's happening. A team member will get back to you soon with more information. Thanks for your patience and for providing such detailed information about the issue! 👍

Send more call id similar to this!!

here is another callId: 57d1372e-bd31-4313-8b3f-b8cc4893fdeb

Hey @daniel, I looked into the recently shared call ID. HIPAA is set to true, so I couldn't view the logs or continue investigating. However, with the previous call ID, it was primarily due to prompting. If you share another call ID, I can conclude my findings and help you better. Why I am asking for another call ID with HIPAA disabled is because according to my past experience, it's mostly because of prompting. In your case, you have strict set to true, requiring variable listing out, and LLM is still a black box. So I want you to be sure on this.