Actions and results.

Inspect the tool

Check its name, input schema and purpose. The public catalog provides reference information; permitted actions depend on the account.

Complete the task

Before changing data, check the workspace, account and arguments. Do not rely on an extra confirmation if the client does not provide one.

Check the result

An operation has a state and a result. Compare the result with the original service; when retrying, consider the selected action's idempotency.

From an accepted request to completion

An execution can have states requested, queued, running, retrying, succeeded, failed, rejected and cancelled; see the Execution schema for the current contract's exact enum. Distinguish admission refusal from provider failure. A result response can include a short-lived signed link for a large payload.

Before retrying a change, check the previous call's outcome. The network can fail after a provider has applied a write. For HTTP methods that support it, use one idempotency key per logical operation; raw proxy and mirror need separate care because a retry creates a new upstream call.

The execution reference describes status, result, attempts and cancellation. Cancelling an operation does not promise to roll back a change already applied in an external service.