-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.Net: Find Associated Tool(s) Called #10654
Comments
Adding @SergeyMenshykh to help. |
@moonbox3 @SergeyMenshykh additionally, can data be pulled as to why the LLM picked which plugin(s)? |
Hi @aherrick, I can think of a few ways to get called functions:
If you just need to identify called functions, go with option 1 or option 2 because it may be easier from an implementation point of view. If you need a little bit more control than just identifying which function was called, such as terminating function invocation or changing the invocation results, go with option 2. If you need full control over interpreting function calls, such as getting a list of functions called, deciding whether to invoke them or not, changing arguments and results, etc., go with option 3. |
@SergeyMenshykh thanks for the detailed response! my thought was that the "result" object that is returned from the |
The issue has been resolved. If you have any other questions or need more help, please reach out. |
I'm trying to figure out the cleanest way to figure out what tools were invoked in a call. Here is what I've come up with but there has to be a better way?
The text was updated successfully, but these errors were encountered: