Tools and workflows

Start with one useful sequence: support request → draft → owner approval → record. This is an integration design example; use the tool connection details confirmed during onboarding rather than treating the legacy API examples as runnable setup.

1. Read the support request

Your product authenticates the user and checks access to the selected ticket. Supply only the fields the agent needs. Keep the customer workspace and allowed tool scope explicit.

2. Prepare a draft

Use the approved model route to draft a follow-up note. Present the draft for review. Generated text does not authorize an external action, and ticket content must not change tool permissions.

3. Require owner approval

Show the request owner the exact destination and note. Let them approve, edit, or reject it. If the destination or content changes, request approval for the revised action. Recheck current business permissions at execution time.

4. Record the approved result

Send only the approved note to the permitted destination. Show success after the destination confirms the write. If the connection fails after dispatch, reconcile the outcome before retrying so the same note is not recorded twice.

Validate before expanding

Exercise an unauthorized ticket, rejected approval, edited draft, unavailable model route, and an ambiguous tool timeout. Decide which records your product keeps and for how long. Confirm implementation support with the Mystro team.

For protocol design background, see the legacy tool contract and legacy approval contract. These remain proposed reference material, not a guarantee that every documented operation is available in your environment.