Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_send_transaction

Executes contract calls or native transfers through the user's smart wallet as an ERC-4337 UserOperation and returns a passkey approval link before on-chain submission.

Instructions

Execute a call through the user's SMART WALLET (Safe) as an ERC-4337 UserOperation. For advanced use (contract calls, native transfers) — for simple token sends use rift_send_crypto instead. REAL TX — confirm with user.

Does NOT execute directly: returns an APPROVAL REQUIRED link the user approves with their passkey. Check with rift_get_approval (result has userOpHash / transactionHash). Never call again to retry.

Semantics an AI MUST know:

  • The on-chain sender is the user's SMART WALLET (a passkey-owned Safe). There is no EOA.

  • The returned 'hash' is a UserOperation hash (NOT a classic Ethereum tx hash). Do NOT link it as etherscan.io/tx/ — that will 404. To track, use a bundler-aware explorer (jiffyscan.xyz/userOpHash/) or poll a bundler via eth_getUserOperationByHash.

  • Gas is sponsored by default. Pass 'paymasterToken' (ERC-20 contract address) to pay gas in a token like USDC instead.

  • After approval, rift_get_approval's result carries userOpHash and transactionHash. Fields 'nonce', 'gasPrice', 'blockNumber' are NOT returned — UserOps don't have them.

Requires login.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>",
      "to": "<to>"
    },
    "name": "rift_send_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesContract or recipient address (0x...)
dataNoEncoded contract call data (hex, starts with 0x)
chainYesChain: BASE, POLYGON, ARBITRUM, ETHEREUM, etc
valueNoNative value in wei (decimal string)
paymasterTokenNoOptional ERC-20 token contract address to pay gas with. Omit for sponsored gas (free to user).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full behavioral burden and does so: it discloses that execution is deferred behind a passkey approval link, that gas is sponsored by default, that the on-chain sender is a Safe with no EOA, and that login is required. It even pre-empts wrong post-processing by explaining the returned hash is a UserOperation hash that will 404 on etherscan and naming bundler-aware alternatives.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical constraints — real transaction, confirm with user, does not execute directly, never retry — are front-loaded in the first two paragraphs, and the bulleted semantics block is scannable. It runs slightly long, with the explorer-hash guidance expanded more than strictly needed, but no sentence is pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema and no annotations, the description covers the return shape (approval link, then userOpHash/transactionHash via rift_get_approval), explicitly lists fields that are NOT returned (nonce, gasPrice, blockNumber), and states the auth requirement. Nothing an agent needs to call and correctly follow up is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 'to', 'data', 'chain', 'value', and 'paymasterToken' are already documented in the schema. The description reinforces paymasterToken ('pass ... to pay gas in a token like USDC') but adds little syntax or format meaning beyond what the schema already states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Execute a call through the user's SMART WALLET (Safe) as an ERC-4337 UserOperation') and explicitly delimits scope against the sibling rift_send_crypto for simple token sends. An agent can distinguish this from rift_sign_transaction and rift_send_crypto without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('advanced use (contract calls, native transfers)'), when-not ('for simple token sends use rift_send_crypto instead'), and a hard operational exclusion ('Never call again to retry'). It also routes the follow-up step to rift_get_approval by name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools