propose_send Production Write
Production (https://mcp.tuyo.com/mcp) serves an earlier version of this tool. This page shows the early-access version.

Description

The model reads this text to decide when and how to call the tool.
Create a send approval request for the user to review in Tuyo; this does not execute payment. Resolve the exact payer, recipient, funding asset and network first; ask about ambiguous names or missing bank details. Saved bank recipients may belong to self, another person or a business. This user-approval path needs no signer or management setup. To pay from a pod you already manage, read all pages of list_managed_pods with the same signer and use prepare_send or prepare_convert instead; never prepare to probe authority. Each call creates a separate request; after an unknown outcome, check list_proposals instead of repeating it. Read get_proposal for the decision and get_transaction for settlement. To trade the user’s own assets, use propose_convert.

Input

object
required
Choose one recipient type. Bank recipients require fiat recipientGets and allow reference; other recipients require token recipientGets and allow memo. Omit optional reference/memo unless requested.
object
required
Bank recipients require fiat; other recipients require token. This is requested receipt, never payer funding or proof of settlement.
object
required
Exactly one owned funding source in the payer account; token and vault fields cannot be mixed.
string
Payer accountId from list_pods or holdings.pods.items[].pod. Omit to pay from main; use the same scope for balance and quote reads.
string
Optional token-send memo; forbidden for bank recipients.
string
Optional bank-only reference. From list_external_bank_accounts accountType: us ≤10 alphanumeric/spaces; sepa 6–140 alphanumeric/spaces and & - . /; clabe ≤40 alphanumeric/spaces.
integer
Approval lifetime in seconds, 60–86400; omission uses 900.
string
Optional short explanation of the user goal. Do not include secrets or full addresses.

Output

The structured result is { data, meta }. meta has the requestId and the asOf time. These are the fields of data. An error returns { error, meta }; see Errors.
object
required
object
required
"user_approval"
required
"not_established"
required
object
required
string[]
required