Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_request_password_reset

Initiate a password reset by sending a one-time passcode to a recovery email or phone, with no login required.

Instructions

Start password reset flow. Sends OTP to recovery email or phone. 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": {
      "externalId": "<externalId>",
      "method": "<method>"
    },
    "name": "rift_request_password_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYesWhich recovery method to use
externalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.5/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 burden, and it does disclose two meaningful traits: an OTP is dispatched as a side effect and authentication is not required. It omits what happens for an unknown externalId, whether it reveals whether a recovery method exists (user enumeration), any rate limits, and whether a reset token or expiry is returned.

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, front-loaded with the action, then the side effect, then the key constraint. Nothing is redundant and the auth exemption is stated emphatically where an agent will notice it.

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 a two-parameter, no-output-schema tool the description covers the essentials, but with no annotations and an undocumented externalId, an agent still lacks the identifier format and the failure behavior it would need to call this 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 coverage is 50%, so the baseline is 3. The description usefully maps the method enum to real channels ("recovery email or phone"), but leaves externalId completely unexplained in both schema and description, which is the more ambiguous of the two required parameters.

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 gives a clear verb and resource ("Start password reset flow") and adds the concrete effect ("Sends OTP to recovery email or phone"). It is distinguishable from rift_reset_password by the word "start", but it never names that sibling, so an agent must infer the pairing on its own.

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?

"Start password reset flow" implies the entry point of a reset and "Does NOT require login" signals an unauthenticated context, which is useful usage framing. It stops short of saying what to do next (e.g. that rift_reset_password completes the flow) or when this should not be called.

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