Hi, I’m getting unexpected behaviour when using the required property in a ‘function calling’ definition, but it may be a misunderstanding of how they should work. It appears that the API will still fire a function call when some ‘required’ properties of my defintion have not yet been inferred and…

I am seeing the same behaviour in multiple cases: One example being as below where the “name” key is not part of the JSON. The output json is: {“confidence” : 1 } Schema is: { "name": `single_name_matched`, "description": `Matched a apple laptop model name`, …

The chat completions endpoint seems less reliable to me compared to the completions endpoint An elaborate chat completion prompt with function calling using 3.5 turbo seems to be worse than da vinci. Da vinci gave me more reliable json on the completions endpoint. It costed more tokens though.

I am also facing this issue, where despite specifying the “required” properties, The function still calls itself and returns with only some of the arguments, with some that had been required being missing. Why does it not comply with the “required” properties? I have tried putting in system message…

Enums seem to work ok for me so far so it seems a validation stage is kicking in, why not for required?

I noticed that “required” and “enums” are not respected. Some of the scenarios are: if there are any typos in the schema. e.g property name is misspelled in some place. if there are special characters in the enum Other cases? It still seems the default completions API is more reliable than chat …

yeah man. I’ve resorted to handling the oft times where there might be a missing argument despite it being ‘required’ in the function itself. Since I have been unable to wrangle both 3 or 4 model to get anywhere close to 95% success rate.

Has anyone had any better luck steering the function via its description in the function definition? Do we get better results if we use something like: { “name”: “DoAThing”, “description”: “Do a thing function that fires when all required property values are captured.”, “parameters”: { “type”:…

Hi, Put yourself in the shoes of the AI, the information you have is that contained in the API you are making at that very second, you have no history and you have no idea of the internal states of your codes parameters and variables. Given that information could you accurately and consistently re…

In this case, we are focussed on the required parameter and user’s experiences with how well it works. Clearly there is some kind of validation layer somewhere that is expected to provide function output if required properties are populated but we are finding that is not always the case - yet enums,…

Problem with 'required' property when function calling

API

sabbadin12 June 28, 2023, 4:00pm 9

Topic		Replies	Views
Function parameter requirements not reliable API function-calling	6	2929	May 27, 2024
Chat gpt function calling, requited parameters are ignored API	10	9617	August 1, 2023
OpenAI function calling make up parameters API	8	7681	September 4, 2023
The Assistant will never recognize a required parameter that is of object type in Function Tools Bugs api , functions , tools	4	1556	February 5, 2024
Gpt-4-turbo is not respecting "required", while gpt-4-turbo-preview is API	14	1923	April 17, 2024

Problem with 'required' property when function calling

Related topics