Power Platform Community Forum Thread Details

I have built a Computer Use Agent (CUA) tool designed to scrape/extract tender details from public procurement websites

(e.g. https://www.gebiz.gov.sg/ptn/opportunity/opportunityDetails.xhtml?code=SPO000ETQ25000184&status=RELEASED&type=TQ&OPPORTUNITY_ID=1000000000000506597&origin=rss ).

Despite clear instructions, I am hitting two technical blockers that are preventing a smooth integration:

1. Non-Deterministic JSON Output

The Problem: The tool is instructed to return data in a strictly formatted JSON string. During testing, the behavior is inconsistent.
- Success: Sometimes it returns a perfect JSON object.
- Failure: Sometimes it returns nothing at all—even when using the exact same URL input. Although from the steps it appears that internally it has compiled the JSON but not presented back.
What I've Tried: Standard prompt instructions within the CUA configuration.
Question: How can I force the CUA to be more deterministic and strictly adhere to the JSON schema without these "no-response" lapses?

2. Returning Data to the Main Agent (Handoff)

The Problem: Currently, the CUA designer in Copilot Studio doesn't seem to have an explicit "Output" parameter section like standard Topics or Power Automate flows do.
The Goal: I need to pass the extracted JSON string back to the Main Agent or a specific Topic so I can parse it and use the variables later in the conversation.
Question: Since there is no native "Output" provision in the CUA tool UI yet, what is the best workaround? Should I be using a global variable, or is there a way to trigger a "Return Value" action within the CUA instructions?