Function calling cookbook does not adequately explain how function calling works #92
Labels
component:quickstarts
Issues/PR referencing quickstarts folder
status:triaged
Issue/PR triaged to the corresponding sub-team
type:bug
Something isn't working
The documentation and the function calling cookbook examples confer the impression that the model will use one of the tool functions supplied by the client in the
function_declarations
array. In fact, the model predicts a tool function and is in no way constrained to use the tools listed.Consider the following request (used in v1beta, gemini-pro)
Model request.json
It generated response like this (Headers and response body)
BadFunctionResponse2.txt
BadFunctionResponse2.json
The actual name of the
functionCall
the model will predict varies. This is another model response to that same identical model requestBadFunctionResponse3.json
The cookbook should, in my opinion, clarify that the function declaration section is not like a traditional software interface with strictly defined operations that specify a contract. The interface is open ended, with the model predicting useful tool functions it considers should be there.
The text was updated successfully, but these errors were encountered: