The idea is:
Reintroducing the input schema and an additional field option for the AI agent calling workflow tool. This change would likely also apply to the HTTP request tool.
My use case:
Complex tools requiring multiple inputs and various formats (like strings, integers, arrays, etc.) necessitate input schemas. After several tests, the call workflow tool v2.0 consistently returns schema errors. Version 1.3 operates smoothly with an input schema. Using the schema as a description in v2.0 isn't feasible due to the 1024-character limit, and including it in the prompt is less reliable and consistent than using the input schema field in the v1.3 node.
I think it would be beneficial to add this because:
AI agents will become significantly more reliable, and I want to ensure this functionality isn't lost as the call workflow tool v1.3 becomes outdated.
Any resources to support this?
Compare the execution of a complex tool using v1.3 with an input schema versus v2.0 without one. The difference is substantial.
Are you willing to work on this?
This involves simply restoring the feature. No additional work is required.