Agent-ready Business Action v2

Expose an existing domain capability to agents through a narrow MCP Workflow rather than giving the agent direct provider credentials or a generic integration surface.

Separate domain and interface

Place the reusable business operation in a Sub-Workflow with typed Parameters and Returns. Add a thin MCP Workflow that validates agent Arguments, calls the domain Workflow, and maps the result into one root MCP respond Step.

This separation lets HTTP, Apps, schedules, or other Workflows reuse the same action without duplicating provider logic or MCP-specific response rules.

Make outcomes deterministic

Use stable business identifiers and explicit state transitions. Return a structured success result and predictable validation, not-found, conflict, and dependency errors. Set IsError for failed tool outcomes while preserving machine-readable details.

For mutations, add idempotency protection and bounded scope. Do not let free-form agent text become a provider command, SQL statement, or unrestricted search.

Apply least privilege

Use a Delegate MCP user API Key scoped to the target Environment, assign only the interface Workflows, and permit only intended users. The backing Connections should use the minimum provider permissions required by the business action.

Verify the complete path

Debug the domain Workflow, then the MCP adapter. Publish and enable both in the same Environment, test delegated discovery and invocation, and inspect the linked logs. Coordinate contract and release changes across the adapter and domain Workflow.

See also

See Create an MCP Tool Workflow, Factor a Large Workflow, and App Security Model.