Can anyone clarify what are some proven practices for returning values from a Dust app?
It seems returning a Boolean can indicate true for success and false for failure.
The docs indicate that a numeric return value can be interpreted in the context of the app's description.
Is there a recommended way for the Dust app to return more structured data (e.g., table of CPI by month) that an agent can understand?
Hi Marty. You can return arbitrary JSON that fits your needs. The key is:
Use a Code block to shape the data, so you don't return a bunch of unneeded things from your curl request
Give good names to the properties, so the LLM can make sense of them
In addition, you can explain what each property means in the app's description
See this end to end demo that covers doing this: https://www.youtube.com/watch?v=NNx1xM-KDDw
Thank you for the tips David Ebbo! I will give this a try.