[Feature Request] Dynamic list capability support in tool contract #383
Assignees
Labels
enhancement
New feature or request
Comments
|
@chjinche is working on it. |
7 tasks
chjinche
added a commit
that referenced
this issue
Oct 23, 2023
# Description Implementing `dynamic_list` contract to unlock the scenario that any tool should be able to define the listing experience and the corresponding request to enable the dynamic listing feature. See more in #383 In this PR, we did following things: - implement `gen_dynamic_list` in `tools_manager`. - append ws triple to function input params, as user may call azure control plane api in the custom function to list Azure resources. - add an example tool with dynamic list input to `my_tool_package`. # All Promptflow Contribution checklist: - [X] **The pull request does not introduce [breaking changes].** - [ ] **CHANGELOG is updated for new features, bug fixes or other significant changes.** - [X] **I have read the [contribution guidelines](../CONTRIBUTING.md).** - [X] **Create an issue and link to the pull request to get dedicated review from promptflow team. Learn more: [suggested workflow](../CONTRIBUTING.md#suggested-workflow).** ## General Guidelines and Best Practices - [X] Title of the pull request is clear and informative. - [X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, [see this page](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md). ### Testing Guidelines - [X] Pull request includes test coverage for the included changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that the LLM has the capability to dynamically list the deployment names based on the AOAI connection provided. It would be advantageous to incorporate this capability into the tool contract, allowing other tools, including custom tools, to benefit from it. For instance, the "Vector index lookup" tool could have the "path" input dynamically list the available ML Indexes in the workspace.
In summary, any tool should be able to define the listing experience and the corresponding request to enable the dynamic listing feature.
The text was updated successfully, but these errors were encountered: