@bradlymathews, you can use the action "Run script" instead of "Control query" and then pass your parameters to the query by using the additionalScope. What you are requesting is the same functionality but in the action "Control query" which doesn't add any real new functionality for developers (since the same exists already in "Run script"). It only makes Retool more attractive and easier to use for new developers since it is easier to spot the possibility to handover parameters to queries. Is my assumption correct?
I have barely used the Run Script option preferring to use separate js queries and transformers for all my code that is more than simple ternaries. In my view the more you can keep your code in one place (the queries list in this case) the better. If you have bits of code scattered all over your app in various components, it makes it more difficult to debug since it is harder to find.
Now if I could keep all of my related JS, SQL queries and transformers in a single file like I do when I build C# classes in Visual Studio, I would be a very happy camper!
For that reason I do still think that having a separate property to pass additionalScope parameters to queries making Control Query equal to query.trigger() would be preferable.
Another thing I would like to add is by my understanding purpose of retool is to make life easy. Yes you can run a script then you can do almost everything by hand.
Was this ever implemented? I second the last opinion, it would make life easier. Having scripts everywhere to call queries with different parameters makes things very messy.