Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_update_recovery

Update existing recovery email or phone methods by verifying identity with external ID and password. Change account recovery details for Rift Finance users.

Instructions

Update existing recovery methods. Requires login + externalId/password for verification (verifyOtp middleware).

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>"
    },
    "name": "rift_update_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYesUser password (required by verifyOtp middleware)
externalIdYesUser external ID
emailRecoveryNoNew recovery email
phoneRecoveryNoNew recovery phone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It usefully discloses that a login plus externalId/password verification through verifyOtp middleware is required, which is real auth context an agent needs. It does not disclose whether supplied recovery fields replace or merge with existing values, what happens when only one of email/phone is provided, or whether the operation is reversible.

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?

Two short sentences, purpose first and auth requirement second, with no filler or redundancy. Every clause carries information.

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 four-parameter mutation tool with no annotations the description covers the essentials an agent needs to call it: what changes and what credentials are required. The remaining gap is partial-update semantics for the optional recovery fields, which is minor given complete parameter documentation. No output schema exists, so return values need not be described.

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 four parameters are already documented, including that password is required by verifyOtp middleware. The description reinforces that externalId/password are verification credentials rather than fields being updated, which is mild added value but largely duplicates 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?

States a specific verb and resource: 'Update existing recovery methods.' An agent knows what the tool mutates. However, it does nothing to separate it from near-identical siblings such as rift_update_recovery_method or rift_add_recovery_method, whose behavior must then be inferred from names alone.

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 tool only applies to recovery methods already configured, which hints at when to use it. But there is no explicit when-not guidance, no pointer to rift_add_recovery_method for new methods, and no mention of prerequisites beyond the login/verification note.

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