About Function Calling deserialization #9620
goranged-intc
started this conversation in
General
Replies: 1 comment 1 reply
-
Hi @goranged-intc, thanks for your question. If I understand correctly, you're asking about how to handle the serialized tool as JSON in your backend like this: {
"type": "function",
"function": {
"name": "DateTimePlugin-GetData",
"description": "Get a Data class.",
"parameters": {
"type": "object",
"properties": {
"data": {
"type": "object",
"properties": {"timestamp": {"type": "object"}},
"required": ["timestamp"],
"description": "The data.",
}
},
"required": ["data"],
},
},
} Is that accurate? The name of the tool is the full qualified name (plugin name - function name, in this example Is my understanding correct here, or am I way off? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello team,
First, some context, our company group has been heavily using SK for the past year and a half. However, we are using it as a backend, we abstract multiple models through it and we expose chat completion, embedding and other services through APIs:
Client -> Inference API -> SK AI Backend -> Provider
Now, it works but now we are trying to enable FUnction Calling for clients using function calling:
Client (Using SK with function calling) -> Inference API -> SK AI Backend -> Provider.
And the challenge is that, since the SK in the client is serializing the tools and passing that in the payload, the SK in the backend is just receiving those tools, but we don't see a way to convert (in the backend) those tools (json) into plugin function with parameters since the functions are not in the context of the backend SK.
Do you know a way to handle the function calling passthrough in the backend?
Best,
Guillermo.
Beta Was this translation helpful? Give feedback.
All reactions