Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_add_recovery_method

Adds a verified email or phone recovery method to a user account, requiring external ID and password for verification.

Instructions

Add a new recovery method (email or phone). 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>",
      "value": "<value>"
    },
    "name": "rift_add_recovery_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesEmail address or phone number
methodYesType of recovery method to add
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 the full burden; it does disclose an authentication prerequisite and a verification step tied to externalId/password, which is meaningful context for a mutation. It stops short of explaining the verification flow (OTP delivery, failure modes), whether duplicates are rejected, or whether the method becomes active immediately — gaps that matter for a write operation.

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, front-loaded with the action and then the prerequisite; every clause carries information and there is no filler or redundant restatement of the tool name.

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?

All four required parameters are covered by schema descriptions and the auth prerequisite is stated, so the agent has enough to attempt the call. Given this is an unannotated mutation with no output schema, the definition should say more about what a successful add returns (e.g., a pending verification state) and how failures surface.

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, and the enum on 'method' constrains the values. The description's mention of email/phone and verification credentials restates the schema rather than adding format rules, validation constraints, or precedence between the 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 states a specific verb and resource ('Add a new recovery method') and narrows the scope to the two supported types (email or phone), so the action is unambiguous. It does not differentiate from nearby siblings such as rift_create_recovery, rift_update_recovery_method, or rift_add_recovery_method's counterpart rift_remove_recovery_method, leaving the agent to guess which of the overlapping recovery tools applies.

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 second sentence supplies a real prerequisite ('Requires login + externalId/password for verification'), which tells the agent what credentials must be on hand before calling. However, there is no when-to-use guidance relative to rift_create_recovery or the update/remove variants, and no stated condition for choosing emailRecovery over phoneRecovery beyond the parameter name.

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