Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_remove_recovery_method

Remove an email or phone recovery method from a Rift Finance account after login and external ID/password verification.

Instructions

Remove a recovery method. Requires login + externalId/password for verification.

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

Input Schema

NameRequiredDescriptionDefault
methodYesType of recovery method to remove
passwordYesUser password (required by verifyOtp middleware)
externalIdYesUser external ID

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, the description carries full behavioral burden; it does add useful context that login plus externalId/password verification is required before removal. It omits irreversibility, whether removing the last method is disallowed, and what happens if the method is absent, which matters for a destructive operation.

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, front-loaded with the action and followed by the auth prerequisite; no filler. Slightly under-specified rather than padded.

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?

Given a simple three-parameter tool with a fully described schema and no output schema, the definition covers action and auth requirement adequately. The remaining gap is the destructive-behavior detail (reversibility, last-method edge case) that a removal tool would ideally disclose.

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 100% and the schema already documents all three parameters including the enum values. The description only restates that externalId/password serve verification, adding little beyond the schema's own note that password is required by the verifyOtp middleware.

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?

Description states a specific verb and resource ("Remove a recovery method"), which cleanly identifies the operation. It does not, however, distinguish it from the closely-named sibling rift_delete_all_recovery, leaving the singular-vs-all scope to be inferred from the wording.

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?

Usage is implied by the mutation verb and the stated login/verification prerequisite, but there is no explicit guidance on when to choose this over rift_delete_all_recovery or rift_update_recovery_method. An agent must infer the scope boundary from the sibling names alone.

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