Skip to main content

Semantic Kernel – Auto function calling

A  few weeks ago I got contacted by someone(Hi Chris!) who was trying to get my Semantic Kernel demo's up and running on his machine. Chris tried to get the application up and running but got some error messages. I used his input to improve the readme file and updated the main branch to simplify the getting started experience.

However there was one specific error he shared that I want to talk about a little more. Here is the screenshot he shared with me:

 


The reason that he got this error is because ‘auto function calling’ was enabled in the code and the model he was using didn’t support this feature.

Remark: I updated the code to disable auto function calling after I got his email.

A good excuse to talk a little more about this feature…

What is (auto) function calling in Semantic Kernel?

With function calling, you give the LLM the option to interact with your existing code. You can do this quite explicit as I explained in my OllamaSharp post but with Semantic Kernel the process is greatly simplified by automatically describing the registered functions and their parameters to the model and then handling the back-and-forth communication between the model and your code. The model itself will decide based on the provided prompt if a specific function should be called or not.

To make this work you need to create a plugin containing one or more KernelFunction methods:

This plugin should be registered in Semantic Kernel:

Auto function calling is enabled by default in Semantic Kernel:

But you can disable it using the following code:

What models can I use that support function calling?

If you are using Ollama, you can use the filter on the Models page to list only models that support tooling:

More information

Function calling with chat completion | Microsoft Learn

wullemsb/SemanticKernel: Demo code for my AI session

Tool support in OllamaSharp

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Col...