Skip to content

Commit c1c3d3b

Browse files
committed
Update README.md
1 parent 94ecab4 commit c1c3d3b

File tree

1 file changed

+1
-1
lines changed
  • petstore/19-function-calling-with-semantic-kernel-and-azure-open-ai

1 file changed

+1
-1
lines changed

petstore/19-function-calling-with-semantic-kernel-and-azure-open-ai/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -283,7 +283,7 @@ async def process_prompt(prompt: str) -> str:
283283

284284
***Summary***
285285

286-
Here we looked at how to enhance our code to leverage Semantic Kernel with Plugins and Function Calling. We saw how Semantic Kernel will generate our JSON for us. We can control the chat history. Notice that these request can get bloated so you will want to consider leveraging classification if you have a great number of functions and/or chat history which can reduce your tokens and bloat.
286+
Here we looked at how to enhance our code to leverage Semantic Kernel with Plugins and Function Calling. We saw how Semantic Kernel will generate our JSON for us. We can control the chat history. Notice that these request can get bloated so you will want to consider leveraging classification if you have a great number of functions and/or chat history which can reduce your tokens and bloat. Other things to consider are what to do with all of our existing/legacy services and business logic? Can we expose those service contracts (APIM perhaps?) and make them part of our function calling flow?
287287

288288
Things you can now do now with this guide
289289

0 commit comments

Comments
 (0)