Skip to content
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

Examples of tool definition and usage. #28

Open
Tyler-R-Kendrick opened this issue Jun 27, 2024 · 0 comments
Open

Examples of tool definition and usage. #28

Tyler-R-Kendrick opened this issue Jun 27, 2024 · 0 comments

Comments

@Tyler-R-Kendrick
Copy link

Problem statement

My team wants to use prompty tool invocation, but we are having difficulty finding documentation on this feature.
We saw that you demoed tool usage around files in the build presentation; but, we didn't see how those tools were defined - or what the limitations of the template syntax were for tool invocation.

Solution Exploration

It appears that jinja2 is specified as the only supported template engine. However, the build demo shows a different template syntax for tool invocation in the yaml portion of a prompty file. The line using string interpolation and file invocation appears to be currently undocumented. It is also unclear if tools other than "file" are able to be registered (or if there are other default tools).

The line I'm referring to reads approx:

sample:
  research: ${file:research.json}

There are many open questions about this syntax. For example:

  • How do tools take in multiple arguments?
  • What are the restrictions for tool names (can they have dashes, spaces, etc?)
  • What are the restrictions for arguments (do they support json object syntax, strings?)

No information about tool invocation was discovered in the markdown portion of the prompt file. Though jinja template syntax should be sufficient, it is uncertain how tools are loaded for execution in this scenario.

The Ask

Provide documentation to clarify how to provide built-in and custom tool invocation for both the yaml and markdown portions of the prompty file where the scenarios are currently supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant