Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_send_crypto

Send crypto to a recipient address by returning an approval link for passkey confirmation, then check approval status before treating the transaction as complete.

Instructions

Send crypto to an address. REAL TRANSACTION — always confirm with user first. Does NOT execute directly: returns an APPROVAL REQUIRED link the user must open and approve with their passkey. Give the link to the user, then check with rift_get_approval. Never call again to retry. No OTP/password needed. 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": {
      "to": "<to>",
      "value": "<value>",
      "token": "<token>",
      "chain": "<chain>"
    },
    "name": "rift_send_crypto"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient wallet address (0x...)
typeNogasless = no gas fee for user (recommended)gasless
chainYesChain: BASE, POLYGON, ARBITRUM, etc
tokenYesToken: USDC, USDT, ETH, etc
valueYesAmount to send (e.g. '10' for 10 USDC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses that it does not execute directly, that a human passkey approval is required, that a link is returned rather than a transaction result, and that retrying is harmful. This is exactly the non-obvious behavior an agent could not infer from the schema.

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

Conciseness5/5

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

The warning is front-loaded ("REAL TRANSACTION — always confirm with user first"), followed by the mechanism and the follow-up step. Every sentence supplies an operational fact; nothing is padded.

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?

Although expensive-irreversible money movement with no annotations and no output schema is a high-risk gap in general, the description compensates by explaining the asynchronous approval return value and the mandatory next step. An agent has everything needed to call it and handle the result correctly.

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 all five parameters including the gasless/normal enum are documented in the schema itself. The description adds no parameter-level meaning, which is acceptable but not value-adding.

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

Purpose4/5

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

"Send crypto to an address" gives a specific verb and resource with a clear scope marker (REAL TRANSACTION). It does not explicitly distinguish itself from the similarly named rift_send_transaction or rift_send_payment_link siblings, so an agent must infer the difference.

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

Usage Guidelines4/5

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

Strong sequencing guidance: tell the user to open the approval link, then poll rift_get_approval, and explicitly 'Never call again to retry.' It also states prerequisites (requires login, no OTP/password). What's missing is a direct contrast with sibling send tools for the case where a different flow is appropriate.

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