Open eyurtsev opened 6 days ago
Hey @eyurtsev! We are a group of students from UofT interested in this issue. Is it possible we could know more details of this issue and the desire output?
A tool is an association between:
There are use cases, where some of the tools inputs should not be controllable by the chat model, but dictated by the application logic. (e.g., user_id
-- should be associated with the user logged into the application and not chosen by the chat model as that would be a (very serious) security vulnerability)
We use special type annotations to mark arguments as "hidden" from the chat model. This allows us to use the @tool
decorator to easily generate a schema that can be presented to a chat model without surfacing other parameters that the chat model should not know about (these parameters will be injected during run time).
FYI I haven't triaged this issue yet to determine whether it manifests itself when used with chat models (there might be another code path used) -- i don't know if this is a high priority issue yet or not, if it's high priority we will likely tackle within a few days time
Privileged issue
Issue Content
schema inspection + special type annotations