Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_reset_password

Reset a Rift Finance account password using an OTP from email or phone recovery, without requiring login.

Instructions

Complete password reset with OTP from recovery method. Does NOT require 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": {
      "username": "<username>",
      "newPassword": "<newPassword>",
      "otpCode": "<otpCode>"
    },
    "name": "rift_reset_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoRecovery email (if using email recovery)
otpCodeYesOTP code from recovery email/phone
usernameYesExternal ID
newPasswordYesNew password
phoneNumberNoRecovery phone (if using phone recovery)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.4/5.0
Behavior3/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. It does disclose a genuinely useful trait — that no login/session is required — but says nothing about whether a recovery email or phone must already be registered, what happens to existing sessions or credentials on success, failure modes for an invalid/expired OTP, or any rate limiting.

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?

Two short sentences with no filler, and the key operational constraint ('Does NOT require login') is given its own emphasized sentence. It is efficient, though the terseness leaves the recovery-method prerequisite unstated.

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

Completeness3/5

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

For an unauthenticated password-reset mutation with five parameters, no annotations, and no output schema, the description covers the core action and the auth exemption but omits the prerequisite flow, OTP expiry/invalid handling, and which recovery inputs are conditionally required. Adequate to attempt the call, not complete enough to use it confidently.

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 all five parameters are already documented by the schema, establishing a baseline of 3. The description adds only the hint that the OTP comes from a 'recovery method', which loosely connects to the email and phoneNumber recovery parameters but gives no guidance on which to supply when.

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?

The description states a specific verb and resource ('Complete password reset with OTP from recovery method'), which is unambiguous and implicitly distinguishes it from the sibling rift_request_password_reset (that tool initiates, this one completes). It stops short of naming that sibling or the prerequisite flow, so the differentiation is inferable rather than explicit.

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

Usage Guidelines3/5

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

The phrase 'with OTP from recovery method' implies this is the second step, to be used once an OTP has been obtained, and 'Does NOT require login' tells the agent it works unauthenticated. However, there is no explicit statement of prerequisites (such as having previously called rift_request_password_reset or having a recovery method registered) and no when-not guidance.

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