Currently Amsters API seems to be execute linear sequence. Now we can sometimes access the result to the groovy script variable and perform some operation and later use Amster command.
Take for example you can run
query Realms --global
realms = _
update .... --id .... --body ....
However, it is quite problematic to run thru loop to say process some realms stuff and then repeated apply some amster command
It would help maybe we expose a "readonly" variable that can be used inside the groovy expression (although if the amster DSL was first class inside the groovy. Somehow it would be best to do something like exposing amster as "object" or the shell