Best practice for developers control over which kernel functions get advertised to the LLM
Opened this issue · 0 comments
markwallace-microsoft commented
Purpose of this task is to provide some guidance and samples for developers on how control which kernel functions get advertised to the LLM
Some options
- Use the tool behaviour which allows the developer specify which functions from the kernel to use.
- Provide an option when plugins/functions are registered to mark them as "not for LLM" e.g. if I have functions I only expected to be called when rendering prompts.
- Exclude the current function, see #6281
- Prevent possible loops