Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_offramp_create_order

Creates a legacy offramp order converting USDC/USDT to local fiat and returns a passkey approval link; confirm with the user and never retry.

Instructions

DO NOT USE — use rift_offramp instead. This is a legacy endpoint that does the same thing. REAL PAYMENT — confirm with user. Returns an APPROVAL REQUIRED link for the user (passkey); never call again to retry.

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": {
      "token": "<token>",
      "currency": "<currency>",
      "chain": "<chain>",
      "recipient": "<recipient>"
    },
    "name": "rift_offramp_create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesREQUIRED. BASE, ARBITRUM, POLYGON, ETHEREUM, CELO
tokenYesREQUIRED. USDC or USDT
amountNoAmount in USDC. Provide this OR localAmount
currencyYesREQUIRED. KES, NGN, UGX, GHS, ETB, CDF, TZS, MWK, BRL
recipientYesJSON string — same format as rift_offramp. See rift_offramp description for per-currency structure
localAmountNoExact fiat payout amount. Provide this OR amount

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.1/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 behavioral burden and does so with high-value disclosures: this initiates a REAL PAYMENT requiring user confirmation, it returns an APPROVAL REQUIRED link tied to passkey flow, and it must not be called again to retry. These are exactly the non-obvious operational traits an agent would otherwise get wrong and duplicate a payment.

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?

Three short sentences with zero waste, and the most consequential instruction ('DO NOT USE') is front-loaded. The payment warning and approval-link behavior follow in priority order, with the retry prohibition last.

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

Completeness4/5

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

For a deprecated duplicate, this covers everything an agent needs to avoid misfiring: the redirect, the real-money warning, and the approval-response semantics. It stops short of describing what the order actually represents (an offramp payout to fiat) or the return payload shape, but with no output schema and a strong steer to the canonical tool, that omission is minor.

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 description coverage is 100%, so the schema already documents all six parameters including required fields and enum value lists. The description adds no parameter meaning of its own; it only redirects the `recipient` structure question to the rift_offramp description. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose3/5

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

The description never states directly what the tool creates; it only says it is a 'legacy endpoint that does the same thing' as rift_offramp, so the actual verb+resource must be inferred from the name and sibling. What it does convey with unusual force is the routing distinction — do not use this, use rift_offramp — which is the most decision-relevant fact for an agent.

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?

It names the alternative explicitly ('use rift_offramp instead') and states the condition that selects it, namely that this one is legacy and equivalent. Combined with the upfront 'DO NOT USE', an agent has an unambiguous routing decision with no inference required.

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