Submit Signed Transaction
sap_submit_signed_transactionSubmit a signed Solana transaction to the network via RPC with configurable retries and confirmation, keeping policy and audit within the MCP server.
Instructions
Submit a signed Solana transaction produced by sap_sign_transaction through the configured RPC endpoint. Use this instead of custom sendRawTransaction scripts so policy, retries, and audit stay inside SAP MCP.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "sap_submit_signed_transaction"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| encoding | No | Input encoding | |
| intentId | No | Optional caller-provided id binding submission, confirmation, and audit output. | |
| commitment | No | Desired confirmation status before returning success. Defaults to confirmed. | |
| maxRetries | No | Maximum RPC send retries | |
| skipPreflight | No | Skip RPC preflight checks | |
| submitRelayUrl | No | Optional submit relay URL. Must be HTTPS, localhost, or 127.0.0.1. | |
| submitViaRelay | No | When true, submit through the hosted OOBE relay. The relay only broadcasts already-signed bytes and never signs. Defaults to false for this local tool. | |
| signedTransaction | No | Signed serialized transaction | |
| confirmationTimeoutMs | No | Bounded confirmation wait in milliseconds. Defaults to 90000; maximum 180000. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | MCP content blocks returned to the caller. | |
| isError | No | True when the tool result represents an application-level error. |