Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_create_recovery

Configure email or phone recovery for an account so users can reset their password later via those verified methods.

Instructions

Set up account recovery methods (email and/or phone). User can later reset their password via these methods. Requires login + OTP.

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_create_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
externalIdYes
emailRecoveryNoRecovery email address
phoneRecoveryNoRecovery phone number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.4/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 the auth requirement (login + OTP) and the resulting capability (password reset). It omits mutation side effects that matter here: whether this overwrites or coexists with existing recovery methods, whether both email and phone can be supplied together, and what happens on partial failure or invalid OTP.

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?

Three short sentences, front-loaded with what the tool does and what it enables, with the precondition last. No filler, though it is arguably too terse for a mutation tool with four parameters.

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 mutation tool with no annotations, no output schema, and two undocumented parameters, the description covers the happy path but not the operational edges. An agent still lacks guidance on overwrite semantics, success/failure behavior, and how this differs from the add/update recovery siblings.

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%: emailRecovery and phoneRecovery are documented in the schema, and the description adds the useful "and/or" optionality hint. But externalId and password are undocumented in both places, and the description never explains what externalId identifies or how the password relates to the OTP flow, so it only partly compensates for the coverage gap.

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 specific verb and resource ("Set up account recovery methods (email and/or phone)") and states the downstream payoff (password reset via those methods). It is clear on its own, but it does not distinguish itself from the closely related siblings rift_add_recovery_method and rift_update_recovery_method, leaving the agent to guess which entry point to use.

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?

"Requires login + OTP" is a useful precondition, so this is more than pure implication. However, there is no explicit when-to-use versus when-not guidance and no sibling alternative is named, even though add/update/remove recovery tools exist and overlap heavily.

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