Add tool calling action types per RFC 004. #149
Conversation
Implements the action abstractions described in RFC 0004: - Add ToolCallAction class for representing tool calls with tool_name and parameters - Add ToolParameter and ToolDefinition classes for action discovery - Add actions() and tools() methods to Environment interface These types enable standardized action discovery and LLM integration for all environment types.
|
Hi @emosenkis! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
meta-cla
bot
added
the
CLA Signed
2 participants
Adds the action abstractions described in RFC 0004:
Adding these will allow anyone building an Environment to use the tool calling concept described in the RFC.
Open question:
Should ToolParameter allow for more complex types, e.g. the parameters of an object or the value type of an array?