You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd like to improve the experience of creating Tools (classes that inherit from Langchain::Tool::Base) for Assistants to use. Open API spec is difficult to compose and we'd like to see if an LLM itself can generate the JSON spec given a Ruby class.
Tasks
Create a .yaml prompt that instructs an LLM to generate a JSON Open API spec (example: database.json) and accepts a Ruby class.
Create a Generator class (under /utils? or maybe new directory /generators?) where this functionality will live.
This Generator class will output a .json file with the generator Open API spec.
The text was updated successfully, but these errors were encountered:
In the Python SDK you can pass functions directly to the model constructor, where the SDK will inspect the type signatures and docstrings to define the tools. For this reason it's important that you correctly type each of the parameters, give the functions sensible names and detailed docstrings.
@andreibondarev Looks great. I can test it for you when ready. A further enhancement could be to make the annotation files optional by looking at the YARD annotations, or for tools that use RBS gem annotations.
Description
We'd like to improve the experience of creating Tools (classes that inherit from
Langchain::Tool::Base
) for Assistants to use. Open API spec is difficult to compose and we'd like to see if an LLM itself can generate the JSON spec given a Ruby class.Tasks
.yaml
prompt that instructs an LLM to generate a JSON Open API spec (example: database.json) and accepts a Ruby class./utils
? or maybe new directory/generators
?) where this functionality will live..json
file with the generator Open API spec.The text was updated successfully, but these errors were encountered: