Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_send_otp

Sends a one-time password to a user's email or phone to verify identity before login, crypto transfer, or offramp authorization. The user must provide the received code to continue.

Instructions

Send a one-time password to user's email or phone. Call this BEFORE: (1) rift_login — to authenticate, (2) rift_send_crypto — to authorize a transaction, (3) rift_offramp — to authorize a withdrawal. The user receives the code via SMS or email and must tell you the code.

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": "rift_send_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoSend OTP to this email
phoneNoSend OTP to this phone number (with country code e.g. +254...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does disclose the key behaviour: the code is delivered out-of-band by SMS or email and the human must read it back. It leaves gaps on what happens when neither email nor phone is supplied (0 required params), whether both can be sent at once, and code expiry.

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?

Front-loaded single-purpose first sentence followed by an enumerated list is easy to scan. The final sentence slightly re-treads the 'SMS or email' point but earns its place by stating the human relay requirement.

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?

With a simple two-param tool, no annotations and no output schema, the description covers what an agent needs to trigger the send and expect a human-supplied code. Naming rift_verify_otp as the next step and the expiry/single-use behaviour would close the remaining gap.

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 both parameters are already documented including the country-code format for phone. The description adds no syntax or selection rule beyond repeating 'email or phone', 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 — send a one-time password to email or phone — and then names the three concrete flows (rift_login, rift_send_crypto, rift_offramp) it gates. An agent can separate this from rift_verify_otp or 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 'call this BEFORE' list with numbered downstream tools gives unambiguous when-to-use guidance. The only omission is that rift_verify_otp is never named as the natural follow-up, but the ordering instruction itself is clear.

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