Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_update_recovery_method

Updates an existing recovery email or phone number for a Rift account after authenticating with the user's external ID and password.

Instructions

Update the value of an existing recovery method. Requires login + externalId/password.

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>",
      "password": "<password>",
      "method": "<method>",
      "value": "<value>"
    },
    "name": "rift_update_recovery_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesNew email or phone number
methodYesWhich method to update
passwordYesUser password (required by verifyOtp middleware)
externalIdYesUser external ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses that this is a mutation requiring login plus externalId/password, but it does not explain whether the old email/phone is invalidated, whether verification is required, whether the change is reversible, or what the operation returns.

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?

The description is two tight sentences, front-loading the action and then the authentication requirement. There is no redundant or filler wording.

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

Completeness2/5

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

For a sensitive recovery-method mutation with no annotations and no output schema, the description is too thin. It covers purpose and authentication, but omits verification flow, side effects on the previous recovery method, and return behavior.

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 four parameters, including the method enum and the new email or phone number. The description reinforces the externalId/password requirement but adds little meaning beyond the schema.

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: updating the value of an existing recovery method. It is clear about what changes (the value), but it does not differentiate this from the close sibling rift_update_recovery.

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 word 'existing' implies this is not for adding a new recovery method, and the description notes the login/credential requirement. However, it does not explicitly say when to use this instead of rift_add_recovery_method, rift_remove_recovery_method, or rift_update_recovery.

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