Bridging Bridge Wormhole
bridging_bridgeWormholeBridge tokens between Solana and EVM chains using Wormhole. Specify source chain, destination chain, token, amount, sender, and recipient.
Instructions
Bridge tokens across chains via Wormhole. Supports Solana ↔ EVM chains. SAP MCP context: Protocol bridging; operation class write. Use for cross-chain asset movement through Wormhole or deBridge. Confirm source chain, destination chain, token mint, amount, recipient, route fees, and finality expectations before invoking a bridge write. For bridge flows call the matching status tool after submission. If the bridge capability belongs to a registered SAP agent, plan the profile with sap_agent_identity_plan, register through sap_payments_register_agent, then advertise bridge capability IDs with sap_payments_update_agent or sap_publish_tool_by_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | Token address on source chain | |
| amount | Yes | Amount to bridge (raw, smallest unit) | |
| sender | Yes | Sender wallet on source chain | |
| recipient | Yes | Recipient address on destination chain | |
| relayerFee | No | Raw token amount (smallest unit, no decimals) | |
| sourceChain | Yes | Source chain identifier (e.g. "solana", "ethereum", "base", "polygon") | |
| destinationChain | Yes | Destination chain identifier |
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. |