#gpt-3.5-turbo making up functions that are not in the "functions" parameter.

8 messages · Page 1 of 1 (latest)

rich portal
#

I'm trying to build a chatbot-like application that can call certain functions, but for some reason this model keeps calling a fucntion called "python" that does not exist, isn't mentioned anywhere in the system prompt, and isn't on the list of available functions passed to it as a parameter. What could be happening?

Thanks.

storm prairie
#

Zero Details, Cannot help. TRy posting your function descriptions because that's most likely where it would be happening.

#
function_descriptions = [
    {
        "name": "WordsAPI",
        "description": "When the user asks for information about a word",
        "parameters": {
            "type": "object",
            "properties": {
                "word": {
                    "type": "string",
                    "description": "The single word that the user had asked about"
                },
            },
            "required": ["word"]
        }
    }
]```
rich portal
#

Ok, here is my function description (I'm only using one function)

[
  {
    "name": "query_database",
    "description": "Hacer querys en SQL a la base de datos para obtener informacion actualizada de precios, concesionarios, fichas tecnicas, etc.",
    "parameters": {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Query a la base de datos en SQL"
        }
      },
      "required": ["query"]
    }
  }
]
storm prairie
#

Not to sound mean, but, open ai works a lot better in english is my initial thought, I'll need to open google translate like openai does to see if i can make more of it.

#
  {
    "name": "query_database",
    "description": "Make querys in SQL to the database to obtain updated information on prices, dealers, technical sheets, etc.",
    "parameters": {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Query to the database in SQL"
        }
      },
      "required": ["query"]
    }
  }
]```

description should be saying what triggers this.
eg.
When the user asks for information about a word

what's the user gotta do to trigger this, Thats the first description

2nd is, Whats needed from that user input to perform the 1st

etc kinda means anything goes.
rich portal
#

This needs to be in spanish, since it's going to be used in a service that's primarily used in spanish. Aditionally, this function description is complemented by a system prompt that describes in detail when the query_database function should be called. In fact, I'm not really having problems with this function at all! It works great. My problem is that, sometimes, the model decides that there's a second function called "python" that can execute python code, and calls it, causing the system to throw an error since no such function exists.

storm prairie
#

In that case, if you are programming it in Python, why not just toss it in a try except, that way if the error happens you can handle it without a crash