Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_update_user

Update a Rift Finance user profile: display name, email, phone, notification email, and auto-swap settings. Email or phone changes require an OTP sent to the new value first.

Instructions

Update user profile. Can change display name, email, phone, notification email, and auto-swap settings. Requires login. Changing email or phone needs an OTP for the NEW value: call rift_send_otp with the new email/phone first, then pass otpCode (changing one of them) or emailOtpCode + phoneOtpCode (changing both). Other fields need no OTP.

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_update_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoNew email (needs otpCode sent to this new email)
otpCodeNoOTP sent to the NEW email or phone, when changing ONE of them
displayNameNoNew display name
phoneNumberNoNew phone (needs otpCode sent to this new phone)
emailOtpCodeNoOTP sent to the NEW email, when changing email AND phone together
phoneOtpCodeNoOTP sent to the NEW phone, when changing email AND phone together
autoSwapEnabledNoEnable/disable auto-swap (auto-bridge incoming USDC/USDT to target chain)
notificationEmailNoEmail for notifications (separate from login email)
autoSwapTargetChainNoTarget chain for auto-swap: BASE, ARBITRUM, POLYGON, or ETHEREUM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the auth requirement, the OTP verification dependency, and which mutations are gated versus free. It does not say whether the update is partial or full replacement, what happens to fields omitted, or whether email change takes effect immediately after OTP — a few behavioral gaps remain for an unannotated mutation tool.

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?

Front-loaded with the core action, then the OTP preconditions in a single dense sentence using parentheses for the one-vs-both branch. No filler, no restatement of the name, and the most error-prone rule (OTP for the NEW value) is emphasized in caps.

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 9-parameter, unannotated mutation tool with no output schema, the description covers the risky parts (auth, OTP workflow) well. It omits that zero parameters are required and that at least one field should be supplied, and says nothing about the response or whether changes are reversible — minor but real omissions.

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

Parameters4/5

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

Schema coverage is 100%, so the per-field descriptions already define each parameter. The description adds genuine above-schema meaning by explaining the mutual exclusivity between otpCode and the emailOtpCode/phoneOtpCode pair, which the schema only hints at field by field.

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?

The description opens with a specific verb+resource ("Update user profile") and immediately enumerates the mutable surface: display name, email, phone, notification email, and auto-swap settings. That field list clearly separates it from siblings like rift_update_recovery or rift_update_recovery_method without needing their schemas.

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 states the prerequisite ("Requires login"), names the alternative tool to call first (rift_send_otp with the NEW value), and branches the flow explicitly: otpCode when changing one of email/phone, emailOtpCode + phoneOtpCode when changing both, and no OTP for other fields. That is a complete when/how routing rule with the conditional alternatives spelled out.

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